Skip to main content
Glama

Recall project context

recall
Read-only

One-call semantic + full-text recall over the graph — a ranked bundle of the decisions, tasks, risks, and documents most relevant to a question or topic. The default way to load context before acting; reach for search only for an exact-term or document-scoped lookup.

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

Input Schema

NameRequiredDescriptionDefault
depthNoBFS depth from seeds (default 1, max 3).
questionYesNatural-language question or topic — e.g. 'help me with monetization' or 'what's the state of auth?'. Embedded for semantic (meaning) search AND tokenized for keyword search; both seed sets are unioned, walked, and returned as one ranked neighborhood.
seed_limitNoCap on seed nodes from each channel (default 10).
max_entriesNoCap on returned nodes (default 30, max 100).
project_slugYesProject slug, e.g. "acme-app" — list(what="projects") returns yours.
hub_edge_limitNoPer-hub edge follow cap (default 12).

Output Schema

NameRequiredDescriptionDefault
dataYesThe action-specific result returned by Stele.
actionYesThe action that produced this result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / properties / data / additionalProperties
      Previous value: -{}New value: +true
  2. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / properties / data / additionalProperties
      Previous value: -trueNew value: +{}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context: it is a one-call union of semantic and keyword seeding followed by a graph walk returning one ranked neighborhood, which tells the agent what to expect in the result without contradicting the annotations.

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, zero filler, and the primary purpose is front-loaded before the alternative-tool routing. Every clause earns its place.

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

Completeness5/5

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

With an output schema present and complete parameter coverage in the schema, the description only needs to convey purpose and tool selection, which it does fully. Nothing required to invoke the tool correctly is missing.

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 baseline is 3. The description alludes to the seeding/walking behavior that the `question` parameter drives but adds no parameter-level syntax, defaults, or trade-offs beyond what the schema already documents for depth, seed_limit, max_entries and hub_edge_limit.

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

Purpose5/5

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

States a specific verb+resource ('semantic + full-text recall over the graph') and enumerates the returned content ('decisions, tasks, risks, and documents'). It also explicitly distinguishes itself from the sibling `search`, so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('the default way to load context before acting') and names the alternative with its selecting condition ('reach for `search` only for an exact-term or document-scoped lookup'). Both sides of the routing decision are covered.

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.