Skip to main content
Glama
inbox-recall

inbox-recall

by joey12725

Read a conversation

get_conversation
Read-only

Reconstruct message threads around a specific message, within a time range, or from the latest messages, and return cursors to continue reading older or newer conversation context.

Instructions

Reconstruct a thread. Pass message_id to read the messages around it (before/after counts), conversation_id with when to read a time range, or conversation_id alone for the latest messages. Returns cursors to keep reading older or newer messages.

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": "get_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
whenNoWith conversation_id: plain-English time range.
afterNo
limitNo
beforeNo
cursorNo
formatNotext: compact, citation-tagged transcript (default). json: the full structured result.text
message_idNo
conversation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new behavior: results are cursor-based and can be paged both older and newer. It does not mention size caps (schema max 200) or any rate/volume limits, so the disclosure is useful but not complete.

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?

Three tight sentences, front-loaded with the core action, then mode selection, then return behavior. Every sentence earns its place with no 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?

There is no output schema, so the description is responsible for describing returns, and it does mention cursor-based continuation; `format` in the schema covers the text/json difference. Minor gaps remain around result size and what a 'thread reconstruction' yields structurally, but nothing blocks a correct call.

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?

With only 25% schema coverage across 8 parameters, the description carries real weight and does explain the crux addressing parameters (message_id, conversation_id, when) and implies before/after as directional counts. It leaves `limit`, `cursor` as an input, and `format` unexplained, though `format` and `when` do have schema descriptions.

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?

The description opens with a specific verb ('Reconstruct a thread') and immediately breaks the tool into three concrete addressing modes (message_id, conversation_id + when, conversation_id alone), which makes the resource and scope unambiguous. It stops short of naming a sibling such as search_messages or get_messages, so an agent must infer the boundary from names alone.

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?

It gives clear, actionable selection guidance among its own three modes: pass message_id to read around a message, conversation_id with `when` for a time range, or conversation_id alone for the latest messages. There is no when-not guidance or explicit routing to alternatives like search_messages, which keeps it out of 5 territory.

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