Skip to main content
Glama

Look up in a RAMen thread

recall_thread
Read-onlyIdempotent

Retrieve saved thread details or draft text by title, or search all threads and memory notes to find where each match is stored.

Instructions

Look up details of saved RAMen threads: the full text of a draft (ask by its title), or anything else that was saved. Without a thread it searches every thread and the user's memory notes, and says where each match is from.

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": {
      "question": "<question>"
    },
    "name": "recall_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadNothe thread's name; leave out to search all of them
questionYeswhat you need, for example 'What time do the shuttles leave?' or 'the invitation draft'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description contributes real behavior beyond them: a fallback that fans out across all threads and memory notes, and that results report provenance ("says where each match is from"). It stops short of describing result shape or how matches are ranked.

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 sentences that are front-loaded with the core purpose before the fallback behavior. Almost every clause carries information, though the parenthetical "(ask by its title)" mildly duplicates the schema's question-parameter example.

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?

For a read-only lookup with a fully documented two-parameter schema and no output schema, coverage is decent: purpose, scope, and the no-thread fallback are all addressed. What is missing is any hint of the response structure beyond provenance tags, such as whether drafts and notes are returned in a unified list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description earns an increment by clarifying the semantics of the optional thread parameter: omitting it does not merely search all threads as the schema says, it also queries the user's memory notes, which is not captured in the schema.

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?

States a specific verb and resource: "Look up details of saved RAMen threads," and enumerates what can be retrieved (full text of a draft by title, or anything else saved). It is clear without naming which sibling to use for adjacent operations like resume_thread or recall.

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

Usage Guidelines3/5

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

Gives implicit guidance by noting that omitting the thread widens the search to every thread plus memory notes, which implies when to supply a thread and when not to. However, it never says when to prefer this over siblings such as recall or resume_thread, leaving that routing to inference.

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