Skip to main content
Glama

Plan with XMemo

recall_plan
Read-onlyIdempotent

Plan which memory searches to execute before retrieval for complex tasks. This optimizes memory access by structuring searches ahead of time.

Instructions

Plan which memory searches to run before retrieval. Use only for complex tasks; for ordinary answers call recall_context or recall directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural-language question or search text.
scopeNoOptional scope that narrows memory access; leave blank for the token default.
bucketNoMemory bucket or namespace to read from or write to; use % only for tools that support wildcard reads.%
team_idNoOptional team/workspace identifier for team-scoped memory access.
memory_typeNoMemory type/category filter or value, such as episodic, identity, procedural, semantic, working, auto, or %.%
output_jsonNoReturn a machine-readable JSON response instead of a human-readable summary.
path_filterNoMemory path filter; % matches all paths.%
prefer_workingNoWhether to prioritize working/session-state memories in retrieval.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that the tool plans searches before retrieval, which is consistent and provides a hint of non-destructive behavior, but does not contradict 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, no redundancy, front-loaded with the core purpose. Every sentence adds value.

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

Completeness4/5

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

Given the tool has 8 parameters and an output schema exists, the description provides a clear high-level purpose. However, it could offer more detail on what 'plan' entails (e.g., output structure), but the output schema and annotations partially compensate.

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%. The description does not add any extra meaning beyond what the input schema already provides for each parameter. Baseline score of 3 applies.

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?

The description clearly states the tool's purpose: 'Plan which memory searches to run before retrieval.' It uses a specific verb ('Plan') and resource ('memory searches'), and explicitly distinguishes from siblings 'recall_context' and 'recall'.

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?

The description provides explicit guidance on when to use ('for complex tasks') and when not to ('for ordinary answers call recall_context or recall directly'), naming specific alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yonro/memory-os-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server