Skip to main content
Glama

recall_context

Search persistent project memory for relevant decisions, recent session handoffs, and developer preferences so AI agents retain context across tools and sessions.

Instructions

Search MindGate (بوابة العقل) using FTS5 BM25 full-text ranking for relevant project decisions, latest cross-agent session handoff, and developer preferences.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recall_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of memories to return (default 10).
queryNoSearch keywords or natural language topic (leave empty to fetch most recent memories).
statusNoFilter by memory status (default 'active'). Pass 'all' to include superseded and deprecated memories.
categoryNoOptional category filter.
workspaceNoProject workspace to search inside.
include_globalNoWhether to also include memories from the 'global' workspace (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that ranking uses FTS5 BM25 full-text search, but it does not state read-only behavior, permissions, result shape, pagination, or how default status/workspace scoping affects results. For a search tool this is adequate but incomplete.

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?

The description is a single front-loaded sentence that names the tool, backend, ranking method, and target content. It contains no filler and is appropriately sized for a search tool.

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?

Given six optional parameters and no output schema, the description identifies what is searchable and how results are ranked. However, it omits when-to-use guidance and does not describe the return shape or scoping behavior enough for an agent to fully predict results. It is minimally adequate.

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 input schema already documents all six parameters, including defaults, enums, and the empty-query behavior. The description does not add parameter-specific meaning beyond the broad content types being searched, so the baseline of 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 states a specific verb and resource: searching MindGate for memories. It also names the kinds of content retrieved (project decisions, session handoff, developer preferences), which makes the purpose clear. It does not explicitly distinguish this retrieval tool from siblings such as get_user_preferences, so it falls short of a 5.

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?

The description explains what the tool searches but gives no explicit guidance on when to use it versus alternatives. There are no when-not-to-use conditions, no mention of sibling tools, and no scenario-based routing. An agent can infer that it is for recall, but that is the only guidance.

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