Skip to main content
Glama
Sign In

mu

by mu.micro
OverviewDiscussionsAdmin

Conversation recall

recall_conversation

Read one whole conversation back by id, as recall_search and recall_list report it

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": {
      "id": "<id>"
    },
    "name": "recall_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe conversation's id, as recall_search reports it
limitNoMax messages, most recent kept (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4/5.0
Behavior3/5

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

No safety annotations are provided; the description indicates a read operation which implies non-destructive behavior. It adds that it returns the whole conversation 'as recall_search and recall_list report it,' but doesn't disclose pagination, rate limits, or auth requirements. Neutral but limited.

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?

Single sentence, front-loaded with action, no redundant words.

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?

Adequate for a simple retrieval tool: schema covers parameters, description references return format via sibling tools. Could mention limit behavior explicitly but schema covers it.

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?

Both parameters are fully described in schema (100% coverage), so the description adds little beyond stating the id-based retrieval. It doesn't clarify limit's interaction with 'whole conversation' beyond schema's default 50.

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 uses a specific verb 'Read' and resource 'one whole conversation' with retrieval by id, and distinguishes from siblings by referencing recall_search and recall_list output format. This clearly identifies the tool's function relative to search/list.

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?

Implies using id from recall_search/recall_list, giving contextual guidance. It doesn't explicitly state exclusions, but the distinction from search/list is evident from the phrasing.

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

All mu toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources