Skip to main content
Glama

Continue a RAMen thread

resume_thread
Read-onlyIdempotent

Brings back a saved RAMen chat so you can continue earlier work; optionally specify a thread or project, or omit the name to reopen the most recent and list others.

Instructions

Bring back a saved RAMen chat, to go on from it here. Use it when the user wants to continue earlier work, a saved chat, a project or a RAMen thread. Without a name it brings the most recent one and lists the others.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resume_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
openNotrue to list the open items of every thread instead
threadNothe thread's name, or words from it; leave out for the most recent
projectNoa project's name: brings back all of its threads together

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact: with no name it returns the most recent thread and lists the others. It does not clarify what "bring back" actually does to the session context, which is the main ambiguity for a resume operation.

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?

Three short sentences, front-loaded with the core action and followed by the usage trigger and default behavior. The middle sentence's list ("earlier work, a saved chat, a project or a RAMen thread") is slightly redundant filler.

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?

For a three-optional-parameter read tool with rich annotations and no output schema, the description covers the action, the trigger, and the no-argument default. The only gap is that the return of the call (what a restored thread looks like) is left implicit.

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 100%, so the schema already documents all three parameters and the baseline is 3. The description reinforces the optionality of the thread name and its most-recent fallback, but adds nothing about the open or project parameters beyond what the schema states.

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?

"Bring back a saved RAMen chat, to go on from it here" gives a concrete verb and resource, and the phrasing about continuing earlier work sharpens it. However, it never distinguishes itself from the sibling recall_thread, which an agent could reasonably read as doing the same thing.

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?

"Use it when the user wants to continue earlier work, a saved chat, a project or a RAMen thread" states the triggering context clearly. There is no when-not guidance and no alternative sibling is named for the overlapping recall case, so it stops short of full routing guidance.

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