Skip to main content
Glama

Recall (relational / graph)

recall_related
Read-only

Answers deep, relational, and multi-hop questions by traversing an entity graph, falling back to slot recall when Neo4j graph projection is unavailable.

Instructions

Answer a DEEP / RELATIONAL / multi-hop question using the entity graph ('who owns the company Bob works for?', 'which services depend on the auth module?'). Uses the Neo4j graph projection when configured; otherwise falls back to slot recall.

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": {
      "question": "<question>"
    },
    "name": "recall_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNo
user_idNodefault
agent_idNo
questionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context — that the tool uses a Neo4j graph projection when configured and otherwise falls back to slot recall — which signals that results depend on deployment configuration. It does not discuss scoping, latency, or failure modes when the graph is absent.

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?

Three tight sentences: purpose first, then inline example questions, then the backend caveat. No filler, and the most decision-relevant content is front-loaded.

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?

An output schema exists, so return-value explanation is not required, and annotations cover the read-only profile. However, for a tool with four undocumented parameters and multi-tenant scoping implied by user_id/agent_id, the description leaves the agent guessing about how the query is scoped.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the schema provides only names and types. The description explains nothing about the three optional parameters — notably user_id and agent_id, which clearly scope whose graph is queried, and run_id. With zero coverage the description was the only place to compensate, and it does not.

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?

States a specific verb and resource — 'Answer a DEEP / RELATIONAL / multi-hop question using the entity graph' — and backs it with two concrete example questions that make the intended scope unambiguous. The 'DEEP / RELATIONAL / multi-hop' framing implicitly distinguishes it from the plain 'recall' sibling, but it never names that alternative, so differentiation is left to inference.

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

Usage Guidelines4/5

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

Gives clear conditions for use: multi-hop questions whose answer spans entities and edges ('who owns the company Bob works for?', 'which services depend on the auth module?'). It also discloses the backend fallback, which tells the agent the answer quality may vary. It stops short of explicit exclusions such as 'use recall for simple single-fact lookups'.

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