Skip to main content
Glama
inboxd
by 47star

get_conversation

Browse conversation previews oldest first by conversation ID, follow next_request to page through results, and open read_request for full message bodies.

Instructions

Browse conversation previews oldest first; follow next_request for subsequent pages.

Use get_recent_records with conversation_id for newest-first browsing. Deleted records are explicitly marked. Open read_request for a full body; no result proves only local absence.

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

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose ordering, pagination continuation, that deleted records are explicitly marked, and the important caveat that an empty result only proves local absence. However, it says nothing about required permissions, result shape, or why the index might be incomplete (sync state), leaving real gaps for an unannotated read tool. The pagination tokens it names ('next_request', 'read_request') also are not the schema's parameter names, which muddies rather than clarifies behavior.

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?

Four short sentences, front-loaded with the ordering and pagination rule and followed by the alternative and the availability caveat; there is little filler. The only structural flaw is the unexplained use of response-field-sounding tokens (next_request, read_request) that make the sentences slightly harder to parse than needed.

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?

There are no annotations and no output schema, so the description is the only source of behavioral context; it covers pagination, ordering, soft-deleted marking, and result-completeness caveats reasonably well. It is not complete, though: with three undocumented parameters it should have explained id scoping and the cursor/limit contract, which is the main thing an agent needs before calling it.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate and largely fails: it never explains what 'id' identifies (conversation id format? source prefix?), what 'limit' means beyond the schema's own default/maximum, or what 'cursor' is. Worse, it refers to 'next_request' for paging while the input schema calls the paging field 'cursor', forcing the agent to guess the mapping.

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 opens with a concrete verb and resource ('Browse conversation previews') and immediately qualifies it with ordering ('oldest first'), so the agent knows exactly what operation this is. It also explicitly distinguishes itself from the sibling get_recent_records by ordering direction, so the two can be told apart without inspecting schemas.

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

Usage Guidelines5/5

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

It gives both a when-to-use rule (oldest-first browsing, paginated via next_request) and a named alternative with its selecting condition ('Use get_recent_records with conversation_id for newest-first browsing'). It also points at read_request when a full body rather than a preview is needed, covering the main branching decisions.

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