Skip to main content
Glama
Sign In
AIOProductOS

AIOProductOS

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
JavaScript
Remote

Read Support Conversation

get_conversation
Read-onlyIdempotent

Retrieve a complete support conversation thread by conversation ID, showing visitor messages and full history oldest first. Resolve the ID via list_conversations first.

Instructions

Read one support conversation: the visitor plus the full message thread, oldest first. Read-only. Resolve the conversation_id first with list_conversations — never guess it.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
conversation_idYesConversation id, from list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.14
  2. Removedv0.1.13
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by specifying the return content (visitor + full thread, oldest first) and the constraint to resolve the ID first, going beyond the structured annotations.

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?

The description is three short sentences, front-loaded with the action and result, and contains no redundant content. Every sentence contributes essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description covers what it returns, ordering, read-only nature, and how to obtain the required ID. Sufficient for an agent to invoke it correctly.

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% with the parameter description already stating 'from list_conversations.' The tool description echoes this but adds the emphatic 'never guess it,' providing marginal value beyond the schema.

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 clearly states the tool reads one support conversation including the visitor and full message thread, ordered oldest first. This distinguishes it from list_conversations (listing) and reply_to_conversation (writing).

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 explicitly instructs to resolve conversation_id via list_conversations and never guess it, providing a clear prerequisite and alternative. While it doesn't contrast with write tools, the read-only instruction and context make usage clear.

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

Deploy Server

Other Tools