Skip to main content
Glama

route

Decides the correct memory operation — remember, correct, or revert — from any utterance, without requiring you to choose the action. Handles ambiguous restatements with configurable policy.

Instructions

ONE-CALL WRITE ROUTER: hand it any utterance and it decides the right ledger operation — a new fact is remembered, a marked correction supersedes, and a revert instruction ("go back to what we had", "restore the original") is resolved against the key's version timeline and executed through the sanctioned revert channel, WITHOUT the caller naming the old value. Use it when you don't want to pick between remember/revert yourself.

The honest limit (measured): an UNMARKED restatement of a superseded value ("the region is osaka", said after the correction) is ambiguous by construction — a stale echo and a deliberate reaffirm can be byte-identical, and no classifier separates them. policy picks the failure mode: "safe" (default) never restores on an unmarked restatement; "context" restores when the preceding turn (pass it as context) shows change-awareness — forgeable, use only if that channel is trusted; "trusting" always restores. Returns {intent, action, key, ...} describing what was done.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNo
textYes
objectNo
policyNosafe
contextNo
capabilityNo
Behavior5/5

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

No annotations provided, so description carries full burden. Explains the behavior for different inputs, the ambiguous restatement case, three policy modes with their failure modes, and return value structure. Highly transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two paragraphs with the main purpose front-loaded. Dense with information but could be slightly more concise. 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 complexity (6 params, no output schema), description covers behavior, policy options, and return format. Missing 'object' and 'capability' explanations, but overall quite complete.

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 coverage is 0%, so description must compensate. It explains 'text', 'policy', 'context', and implies 'key'. However, 'object' and 'capability' are not mentioned, leaving gaps for half of the parameters.

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 it is a 'ONE-CALL WRITE ROUTER' that decides between remember and revert based on the utterance. It specifies what it does: handles new facts, corrections, and reverts without requiring the caller to choose.

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

Usage Guidelines4/5

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

Explicitly says 'Use it when you don't want to pick between remember/revert yourself.' Mentions policy options and the ambiguous case. Does not contrast with siblings like remember/revert but implies it is a meta-tool.

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/DanceNitra/mnemo'

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