Niches · Company knowledge & data catalogues
Record what the agent learned: descriptions, tags, glossary terms or card edits
One company's docs show a full fit.
What counts as done
The write is applied or held for review as reported, a preview is shown before it, failures come back as errors, and the change is findable by search within the index lag.
How agents ask for it: add a description to this table
, tag these columns as PII
, update the onboarding card with the new process
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Hexis Cloud D Bevelites GmbH | Agents write on a draft branch that opens a change request people approve in the app, check canWrite first, and get a saved-locally error when sharing is refused, with an instruction not to report it as shared. Changes are greppable once on the branch. source |
Does the job, with a limit 7
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Atlan C Atlan Pte. Ltd. | Write tools return a preview and wait for approval, and read-only mode removes them on request, but bad glossary input returned an error with isError false that agents took for an answer (acc-32). source |
| Collibra B Collibra Inc. | create_asset and edit_asset write assets with destructive annotations, and data-quality writes have a confirm preview, but edit_asset has no preview, failures come back in an error field, and search lag after a write is not stated. source |
| DataHub C Acryl Data, Inc. (d/b/a DataHub) | Write tools are off unless TOOLS_IS_MUTATION_ENABLED is set, carry readOnlyHint false, and proposals hold changes for review, but save_document and update_description report success while writing nothing (issues 211, 200) and saved documents miss search (acc-26). source |
| Dust B Permutation Labs | The API upserts documents into data sources (under 120 a minute) and MCP tools create files, so learned text can be stored and synced in minutes, but no preview, review hold or error contract for writes is documented. source |
| Guru D Guru Technologies, Inc. | MCP tools Create Draft and Update Card, which suggests updates, keep edits for review. No preview step or error behaviour is documented, and user tokens can write directly through REST. source |
| Marmot B Marmot Data Ltd | Writes preview the exact before and after with confirm false and refuse with isError true without the manage permission, but confirm is a plain flag the server doesn't tie to a review, and the tools carry no destructive annotations. source |
| OpenMetadata C Collate, Inc. | create_entity, patch_entity and create_lineage write under the user's role, and operator tool restriction is merged (issues 36577, 37161), but patch_entity reports a write held for approval as applied (issue 37757) and there is no preview step. source |
Couldn't check 3
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Cohere North D Cohere Inc. | Automations and connectors could write to apps, but no readable page describes writes with preview and errors; the docs are closed by robots.txt. |
| Precisely AI Studio F Precisely Incorporated | Whether any governance asset writes descriptions or tags isn't on the readable page; the help centre couldn't be read. |
| Secoda E Secoda, Inc. | The MCP server registers no write tool; the REST API's edit endpoints were described in an earlier reading but were not re-read under Secoda's Terms of Use. source |
Doesn't do this job 9
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Alation C Alation, Inc. | Release 1.0.0 removed update_catalog_asset_metadata and check_job_status from the SDK, leaving no metadata write tool in the local server. source |
| Basedash MCP B BaseDash Inc. (Delaware, United States) | Writes create and edit dashboards and charts, not catalogue descriptions, tags or glossary terms. source |
| ClicData MCP F ClicData SAS | The MCP page says building in ClicData from the AI client is coming later, so nothing writes descriptions, tags or terms today. source |
| Gemini Enterprise B Google LLC | Not aimed at recording descriptions, tags or cards; no write-back with preview and errors is documented for the API in the pages read. source |
| Glean B Glean Technologies, Inc. | Writes are artifacts saved to a user's Library and connected-tool actions through run_tool, not descriptions, tags or cards on indexed content. source |
| Onyx B DanswerAI, Inc. | The MCP scope is read:search only, with no write tools; documents pushed through the Ingestion API were not visible to MCP search (acc-38). source |
| Overclock F Overclock Technologies Limited | The server is read-only: tools retrieve and never create, change or delete, under scope engine:read. source |
| Procore AI Go F Procore Technologies, Inc. | The support page says the app cannot create or update Procore items or take other actions. source |
| Lens (Thought Industries) F Thought Industries, Inc. | The API creates, edits and syncs sources, but nothing writes descriptions, tags or card edits into the knowledge itself. source |
What stops agents finishing
- write tools listed with no read-only switch (OpenMetadata)
- a write held for approval reported as applied (OpenMetadata issue 37757, maintainer-filed)
- confirm flag the server does not tie to a review (Marmot)
Around it
Before: company-knowledge.find-data-asset, company-knowledge.lineage-trace. After: company-knowledge.find-data-asset.
Where this comes from
Weight 6 of 100 in Company knowledge & data catalogues: 3 of 38 counted accounts (DataHub documents not searchable after write, Atlan glossary errors reported as success, DataHub document search empty); vendor write tools in Atlan, Collibra, Secoda, OpenMetadata, Marmot, Hexis and Guru
The same as data: /api/v1/use-cases/company-knowledge.catalogue-write-back.json, or the MCP tool get_use_case with id company-knowledge.catalogue-write-back. Other jobs in this category: /api/v1/niches?category=company-knowledge.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.