Skip to main content
Glama

Coline

Show messages

show_conversation
Read-onlyIdempotent

Shows the person's channels and direct messages inside the chat, or one conversation or thread, where they can read and reply. Use it when they want to catch up on or answer messages.

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": {
      "workspace": "<workspace>"
    },
    "name": "show_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
threadIdNoA message id whose thread to use.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conversationIdNoFrom list_conversations.

Output Schema

NameRequiredDescriptionDefault
openYes
conversationsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is fully covered. The description adds only that the target is a place to 'read and reply', which is UI framing rather than tool behavior. It says nothing about pagination, what happens when neither conversationId nor threadId is supplied, or whether a full listing is returned by default.

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?

Two sentences with no filler, and the scope (all conversations vs one conversation/thread) is front-loaded ahead of the usage note. The phrasing 'the person's channels' is slightly awkward but costs nothing in length.

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?

An output schema exists, so return values need no explanation, and the annotations cover safety. What is missing is resolution of the scope ambiguity: the description never says whether omitting conversationId and threadId yields the full list, nor how the type filter changes the result. For a 4-parameter read tool with two overlapping selectors, that gap matters.

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 75% and three of four parameters carry inline descriptions, so the schema largely does the work. The description contributes no meaning about the type enum ('channel' vs 'dm'), how threadId and conversationId interact, or which of them wins if both are passed. That leaves the non-trivial parameter combination unexplained.

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 names a concrete verb and scope: it lists the person's channels and DMs, or narrows to a single conversation or thread. That is more specific than a restatement of the name 'show_conversation'. It stops short of distinguishing itself from near-neighbors like read_conversation or search_messages, so an agent must guess whether 'shows' includes message bodies.

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?

"Use it when they want to catch up on or answer messages" supplies a when-to-use condition, but gives no exclusions. Nothing tells the agent when to prefer search_messages or read_conversation instead, even though those siblings plausibly overlap with this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources