Skip to main content
Glama
Sign In
Neotoma

Neotoma

by markmhendrickson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

retrieve_related_entities

Retrieve all entities linked to a starting entity via relationship paths. Traverse direct or multi-hop connections to uncover related data.

Instructions

Retrieve entities connected to a given entity via relationships. Supports n-hop traversal.

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_id": "<entity_id>"
    },
    "name": "retrieve_related_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_hopsNoMaximum number of relationship hops (1 = direct, 2 = 2-hop, etc.)
directionNoDirection of relationships to traverseboth
entity_idYesStarting entity ID
include_entitiesNoWhether to include full entity snapshots in response
relationship_typesNoFilter by relationship types (e.g., ['PART_OF', 'REFERS_TO']). If empty, includes all types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.0
  2. Removedv0.14.0
  3. Addedv0.12.1
  4. Removedv0.11.0
  5. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully convey behavior. It states it retrieves entities, implying read-only, but does not mention performance implications of large max_hops, error handling, or response structure. The lack of behavioral details leaves agents uncertain.

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

Conciseness5/5

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

Two sentences, front-loaded with purpose and key capability. Every word is informative and necessary.

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

Completeness2/5

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

Despite having 5 parameters and no output schema, the description is too brief. It omits what the response contains (e.g., entity snapshots, relationship info) and doesn't clarify the role of 'include_entities'. For such complexity, more detail is needed.

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 description coverage is 100%, so the schema already documents parameters well. The description adds only high-level context ('n-hop traversal') but no extra parameter-level meaning. Baseline 3 is appropriate.

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

Purpose4/5

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

The description clearly states it retrieves entities connected via relationships, and mentions n-hop traversal. However, it does not differentiate from similar sibling tools like 'retrieve_graph_neighborhood', which likely serves a similar purpose.

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

Usage Guidelines3/5

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

The usage is implied: use when you need connected entities with support for multiple hops. No explicit guidance on when not to use it (e.g., when only direct relationships are needed, or when to prefer 'list_relationships' or 'retrieve_entity_snapshot').

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

Deploy Server

Other Tools