Retrieve a stored fact from a previous session using its exact ID. Use this action to access persisted context from past interactions when the precise remembered value is needed.
Retrieve a fact stored in a previous session by id. Exact lookup — not fuzzy or substring.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The exact id a previous remember call used. Returns the stored text, or a "no memory for <id>" message if nothing matches. |
Changes observed during successful MCP inspections.
v0.6.2Input schema / properties / id / descriptionAdded value: +"The exact id a previous remember call used. Returns the stored text, or a \"no memory for <id>\" message if nothing matches."v0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. 'Retrieve' conveys a read-only action, 'exact lookup' clarifies matching semantics, and the schema property description discloses the not-found response. This is adequate transparency for a simple lookup tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no wasted words. The action and resource are front-loaded, and the precision qualifier is presented immediately after the main purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter lookup tool, the description plus schema property cover the operation, id semantics, and missing-id outcome. It could be more explicit about when to prefer this over sibling tools, but nothing essential is missing for a correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the id property already explains that it is the exact id from a previous remember call and what value will be returned. The description's 'exact lookup — not fuzzy or substring' reinforces behavior but adds little new parameter-level meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Retrieve') and resource ('a fact stored in a previous session by id'), and the exact-lookup qualifier distinguishes it from fuzzy search behavior. It clearly positions this as the retrieval counterpart to remember.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for looking up a previously stored fact by exact id, but it does not explicitly say 'use this when you have an id from remember' or name an alternative for fuzzy/substring needs. The 'not fuzzy or substring' hint provides context but not concrete when-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.