Read a cursor-paged conversation transcript; pass the next cursor back for exactly-once, duplicate-free page reads.
Read a cursor-paged transcript page; pass next back for exactly-once reads.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | ||
| limit | No | ||
| conversationId | Yes |
Changes observed during successful MCP inspections.
v0.2.18Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, it discloses important behavioral details: results are cursor-paged and passing 'next' back enables exactly-once reads. This adds real semantic value about pagination and consistency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. Every phrase contributes meaning: what is read, how it is paged, and how to continue reading.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
It is adequate for a read-only pagination tool, but it leaves a gap between the described 'next' cursor and the schema's after parameter. It also does not mention how to request the first page or what the response contains.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, but it only refers to a 'next' cursor without mapping it to the actual after parameter. It does not explain what after, limit, or conversationId mean in practice.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action and resource: reading a cursor-paged transcript page. It clearly distinguishes the tool from conversation_list and conversation_send by naming the paged transcript-read behavior.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives clear usage context by explaining the cursor-paging pattern and instructing the caller to pass 'next' back for exactly-once reads. It does not explicitly contrast this with sibling tools, so it falls just short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.