Skip to main content
Glama

recall_entity

Retrieve all facts stored for a given entity using algebraic unbinding, so agents can recall entity relationships across sessions and identify what is known about a specific person, place, or concept.

Instructions

Probe all facts associated with an entity using HRR algebraic unbinding.

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": "<entity>"
    },
    "name": "recall_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
entityYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are supplied, so the description must carry the full behavioral burden, and it does not. It says nothing about whether results are exact or approximate (relevant given the 'algebraic unbinding' framing), what order facts are returned in, whether a missing entity errors or returns empty, or any cost/latency characteristics. The single technical phrase hints at a mechanism without telling the agent anything actionable.

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?

It is a single front-loaded sentence with no padding, which is structurally fine. However, the space is spent on opaque terminology ('HRR algebraic unbinding') rather than on the scoping and parameter details an agent actually needs, so brevity here is achieved by omission.

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?

An output schema exists, so return-value detail is not required. But with zero annotation coverage, zero schema description coverage, and no guidance relative to five similar siblings, the definition leaves the agent without the information needed to choose this tool or call it correctly.

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%, so the description is the only source of parameter meaning, and it explains neither parameter. It does not clarify whether 'entity' is a canonical name, an ID, or a free-text string, nor that 'limit' caps the number of returned facts and defaults to 8. This is a meaningful gap for a 2-parameter tool.

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?

It names a verb ('Probe') and a resource ('all facts associated with an entity'), so the retrieval intent is inferable, but 'Probe' is vague and the phrase 'HRR algebraic unbinding' is unexplained jargon. It makes no attempt to distinguish this from siblings such as search_facts, get_fact, or list_facts, so an agent cannot tell which retrieval path is correct.

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 and no alternatives are named, despite five sibling tools that also return facts. The only implicit signal is that this tool is entity-scoped while the search_* tools are presumably query-scoped, but the description never states that contrast.

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