Skip to main content
Glama
inbox-recall

inbox-recall

by joey12725

Get messages by id

get_messages
Read-only

Fetch specific messages by ID to verify citations, with optional surrounding conversation context for accurate source checking.

Instructions

Fetch specific messages by id (to verify a citation), optionally with context.

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": {
      "ids": "<ids>"
    },
    "name": "get_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
formatNotext: compact, citation-tagged transcript (default). json: the full structured result.text
contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds the citation-verification framing and notes context is optional, but says nothing about output shape, ordering, or behavior for unknown ids — those gaps are modest given the read-only annotation.

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?

A single front-loaded sentence with the resource and scope established immediately and the rationale in parentheses. No wasted words, though the parenthetical is doing double duty as both purpose and usage hint.

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 simple read-only lookup with no output schema and only three parameters, the description is close to sufficient but leaves the context parameter's behavior and the result shape (transcript vs JSON) to be inferred. A brief note on what context returns would close the remaining gap.

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 description coverage is only 33%: the format parameter is fully documented in-schema, while ids and context are not. The phrase 'optionally with context' is the only signal that context pulls surrounding messages, and even the 0-25 bound is left to the schema; ids semantics (up to 100, plural) are not explained at all.

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 with a scoping qualifier: 'Fetch specific messages by id', plus a stated intent ('to verify a citation'). This distinguishes it reasonably from list-style siblings, but it never names or contrasts with get_conversation, which is the nearest alternative for retrieving message content.

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?

The parenthetical 'to verify a citation' implies when to reach for this tool (you already have ids), which is useful context. However, there is no explicit when-not guidance and no named alternative for the case where the agent has a conversation id rather than message ids.

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