Niches · Company knowledge & data catalogues
Find who owns a thing or who to ask
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
A named person or group with contact handle and the field it came from (owner, steward, author, assignee), and structured filters on those fields work through the agent interface.
Measured, for our own tests: the owner comes back in one call. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: who owns this table
, who should I ask about the billing service
, what's Max's GitHub username
, which tickets did Priya raise today
Does the job, with a limit 10
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 |
|---|---|
| Alation C Alation, Inc. | The lineage guide says to call the Aggregated Context tool for stewards or an owner custom field, but no response showing a contact handle and its source field was read. source |
| Atlan C Atlan Pte. Ltd. | get_assets returns owners and get_users resolves an owner GUID to a person by name, email or username, but that is two calls rather than one. source |
| Collibra B Collibra Inc. | get_asset_details returns responsibilities (role, user or group, inherited) in one call, but by UUID only, usernames without email, and the only owner filter is the Data Steward role on column search. source |
| DataHub C Acryl Data, Inc. (d/b/a DataHub) | get_entities returns ownership and documents can be filtered by owner, with 'who owns' given as an example, but the response's contact handle wasn't seen and get_entities has open failures on larger catalogues (issue 179). source |
| Glean B Glean Technologies, Inc. | employee_search finds people, and REST documents carry author, owner, assignedTo and updatedBy with facet filters. MCP output has no schema and fields can change in any release, and acc-40 says the people graph misses real subject experts. source |
| Guru D Guru Technologies, Inc. | Card documents in answers carry owner, lastModifiedBy and verifiers, which names who to ask about a card. That covers Guru content only, and whether the MCP tools return these fields wasn't readable without signing in. source |
| Hexis Cloud D Bevelites GmbH | access.md names each folder's owner principals and list_file_changes names who changed a file and when, but that takes several calls, covers repository pages only, and there are no structured owner filters or contact handles. source |
| Marmot B Marmot Data Ltd | find_ownership answers in one call for an asset, user or team, both ways, but the formatted result gives the owner's name and type with no email or handle. source |
| Onyx B DanswerAI, Inc. | Chat answers people questions such as a colleague's GitHub username (acc-07), but MCP results carry no author, owner or assignee and drop the tags filter, so which tickets X raised can't be asked through MCP (acc-24). source |
| OpenMetadata C Collate, Inc. | Owners are entity fields that search_metadata and get_entity_details return, and get_user_context gives the caller's teams, but whether an owner's email or handle comes back in the same call wasn't seen, and filters take raw OpenSearch DSL. source |
Couldn't check 5
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| ClicData MCP F ClicData SAS | No owner or people fields are described on the readable page, and the tool list couldn't be read. |
| Cohere North D Cohere Inc. | No readable page says whether results carry author or owner fields or whether people lookup exists; the docs are closed by robots.txt. |
| Gemini Enterprise B Google LLC | The pages read don't describe a people or owner lookup through StreamAssist, or which author fields references carry; people search docs were not opened. |
| Precisely AI Studio F Precisely Incorporated | Nothing on the readable page about owner or steward lookups, and the help centre couldn't be read. |
| Secoda E Secoda, Inc. | retrieve_entity returns whatever Secoda's API sends; whether owners and stewards come back, and in which fields, isn't in the repo, and the API reference was not re-read. source |
Doesn't do this job 5
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Basedash MCP B BaseDash Inc. (Delaware, United States) | No owner, steward or people lookup among the tools; dashboards and charts are listed without documented owner fields. source |
| Dust B Permutation Labs | The Document schema has title, source_url, timestamp, tags and parents but no author, owner or assignee, and the MCP tools listed include no people lookup. source |
| Overclock F Overclock Technologies Limited | deep_search walks people and company entities named in documents, but results carry no author, owner or assignee field and no filter on one. source |
| Procore AI Go F Procore Technologies, Inc. | A person can ask which submittals need their approval in the app, but an agent cannot call it and no owner or assignee fields are returned to one. source |
| Lens (Thought Industries) F Thought Industries, Inc. | Results carry title, excerpt and URL only, with no author, owner or assignee fields and no filters. source |
What stops agents finishing
- MCP results drop author and assignee fields the index holds
- owner fields empty because nobody maintains them
Around it
Before: company-knowledge.find-data-asset. After: chat.send-message, email.send.
Where this comes from
Weight 6 of 100 in Company knowledge & data catalogues: 3 of 38 counted accounts (Onyx people lookup, Onyx MCP dropping reporter and assignee, Glean people graph limits); low because most catalogue accounts mention owners only in passing
The same as data: /api/v1/use-cases/company-knowledge.find-owner.json, or the MCP tool get_use_case with id company-knowledge.find-owner. 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.