Skip to main content
Glama

Find related entities

find_related
Read-onlyIdempotent

Subjects, people, places and projects connected through shared records. Per-corpus counts deduplicate each record; subject/person seeds also include publications, subject/place/person seeds Cluster Chronicles works. Returns ambiguity and cited samples.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_type": "<entity_type>",
      "value": "<value>"
    },
    "name": "find_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoCap on each related_* list, default 20, max 50; sample lists show at most 10
valueYesThe entity to pivot on. subject: substring of a heading ('Islam'). location: any level of the city→country hierarchy ('Nigeria' includes Lagos items). person: a name in either order, accent-insensitive ('Beier, Ulli'). project: an Omeka id ('37700'), a legacy key, or the project name or whole words of it. research_item: an item id ('27733' or 'research_item:27733'), not a text query. record: an omeka_id or typed id ('publication:29919')
entity_typeYesWhat the value denotes. Tags are merged into subjects. research_item: the id of an ILAM African Music article, related by full text. record: any embedded record, related by meaning

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / entity_type / description
      Previous value: -"What the value denotes. Tags are merged into subjects. research_item: an ILAM African Music article, by full text. record: any embedded record, by meaning"New value: +"What the value denotes. Tags are merged into subjects. research_item: the id of an ILAM African Music article, related by full text. record: any embedded record, related by meaning"
    • changedInput schema / properties / limit / description
      Previous value: -"Per-list cap, default 20, max 50"New value: +"Cap on each related_* list, default 20, max 50; sample lists show at most 10"
    • changedInput schema / properties / value / description
      Previous value: -"The entity to pivot on. subject: substring of a heading ('Islam'). location: any level of the city→country hierarchy ('Nigeria' includes Lagos items). person: a name in either order, accent-insensitive ('Beier, Ulli'). project: an Omeka id ('37700'), a legacy key, or a substring of the project label. record: an omeka_id or typed id ('publication:29919')"New value: +"The entity to pivot on. subject: substring of a heading ('Islam'). location: any level of the city→country hierarchy ('Nigeria' includes Lagos items). person: a name in either order, accent-insensitive ('Beier, Ulli'). project: an Omeka id ('37700'), a legacy key, or the project name or whole words of it. research_item: an item id ('27733' or 'research_item:27733'), not a text query. record: an omeka_id or typed id ('publication:29919')"
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / entity_type / description
      Previous value: -"What the value denotes. Tags are merged into subjects. research_item: an ILAM African Music article, by full text"New value: +"What the value denotes. Tags are merged into subjects. research_item: an ILAM African Music article, by full text. record: any embedded record, by meaning"
    • changedInput schema / properties / entity_type / enum
      Previous value: -[
      -  "subject",
      -  "location",
      -  "person",
      -  "project",
      -  "research_item"
      -]New value: +[
      +  "subject",
      +  "location",
      +  "person",
      +  "project",
      +  "research_item",
      +  "record"
      +]
    • changedInput schema / properties / value / description
      Previous value: -"The entity to pivot on. subject: substring of a heading ('Islam'). location: any level of the city→country hierarchy ('Nigeria' includes Lagos items). person: a name in either order, accent-insensitive ('Beier, Ulli'). project: an Omeka id ('37700'), a legacy key, or a substring of the project label"New value: +"The entity to pivot on. subject: substring of a heading ('Islam'). location: any level of the city→country hierarchy ('Nigeria' includes Lagos items). person: a name in either order, accent-insensitive ('Beier, Ulli'). project: an Omeka id ('37700'), a legacy key, or a substring of the project label. record: an omeka_id or typed id ('publication:29919')"
  3. Changed2 schema fields changed
    • changedInput schema / properties / entity_type / description
      Previous value: -"What the value denotes. Tags are merged into subjects — there is no tag pivot"New value: +"What the value denotes. Tags are merged into subjects. research_item: an ILAM African Music article, by full text"
    • changedInput schema / properties / entity_type / enum
      Previous value: -[
      -  "subject",
      -  "location",
      -  "person",
      -  "project"
      -]New value: +[
      +  "subject",
      +  "location",
      +  "person",
      +  "project",
      +  "research_item"
      +]
  4. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  5. Changed1 schema field changed
    • addedInput schema / properties / value / maxLength
      Added value: +1000
  6. First observed

TDQS

B3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (read-only, idempotent, closed-world), and the description adds genuinely non-obvious behavior: per-corpus counts deduplicate records, the set of related entity types varies by seed type (subject/person seeds pull in publications; subject/place/person seeds also pull Cluster Chronicles works), and it returns ambiguity plus cited samples. The phrasing is telegraphic, but it discloses result composition that no annotation or schema field provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, and the core resource is front-loaded. However, the second sentence is compressed to the point of opacity — "subject/place/person seeds Cluster Chronicles works" is missing a verb and forces re-parsing, which costs more than the words saved.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing returns, and it does mention deduplicated counts, ambiguity, and cited samples. But for a tool with six entity types and seed-dependent relationship behavior, it is too terse about how results are shaped and ordered, leaving an agent with an incomplete mental model of the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents value formats per entity_type (substring, hierarchy level, name order, Omeka ids) and the limit cap. The description adds only indirect semantic hints by referring to "subject/person seeds" and "subject/place/person seeds", which reinforces the entity_type enum but gives no syntax or format detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ("Subjects, people, places and projects connected through shared records") but is a verbless noun phrase, so the operation itself — pivot from a seed entity to related entities — must be inferred from the title and schema. It never distinguishes itself from close siblings like get_entity_graph, get_similar_items, or resolve_entity, which an agent could easily confuse with this.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance at all — nothing says whether to call this instead of get_entity_graph, get_similar_items, or resolve_entity. The only implicit guidance is the seed-type list, which implies pivoting from an existing entity, but no exclusions or preconditions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.