Swarm

List conversation entries

swarm_list_conversation_entries

Read-onlyIdempotent

Read thread messages; get thread_id from swarm_get_conversation. entry_id selects one message. Only swarm_mark_thread_read advances the read position.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "swarm_list_conversation_entries"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size; follow next_cursor for more.
`cursor`	No	Previous next_cursor; keep filters and order.
`entry_id`	No	Entry ID from swarm_list_conversation_entries.
`thread_id`	Yes	Thread ID from swarm_get_conversation.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedInput schema / properties / cursor / description

Previous value: -"Previous next_cursor; same filters and order."New value: +"Previous next_cursor; keep filters and order."

changedInput schema / properties / limit / description

Previous value: -"Page size."New value: +"Page size; follow next_cursor for more."

Changed4 schema fields changedOct 29, 2026
- addedInput schema / properties / cursor / description
```
Added value: +"Previous next_cursor; same filters and order."
```
- addedInput schema / properties / entry_id / description
```
Added value: +"Entry ID from swarm_list_conversation_entries."
```
- addedInput schema / properties / limit / description
```
Added value: +"Page size."
```
- addedInput schema / properties / thread_id / description
```
Added value: +"Thread ID from swarm_get_conversation."
```
First observedOct 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description nonetheless adds a non-obvious behavioral fact that reading does not advance the read cursor, which prevents a real agent error. It does not mention ordering, result shape, or whether unread messages are included, which with an output schema and 100% annotation coverage is a minor gap rather than a critical one.

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?

Three short clauses with zero filler; the core purpose and the sibling routing are front-loaded and the read-position caveat follows. Every sentence carries distinct information.

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

Completeness4/5

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

For a 4-parameter read tool with a full output schema and complete annotation coverage, the description covers purpose, source of IDs, single-entry selection, and the read-cursor caveat. Only pagination/order expectations are unaddressed, and those are partly covered by the schema's cursor and limit descriptions.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds provenance meaning beyond the schema: thread_id traces to swarm_get_conversation and entry_id narrows the result to a single message ("entry_id selects one message"). It says nothing about limit/cursor semantics, but those are already documented in 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?

States a specific verb and resource ("Read thread messages") and immediately situates it against siblings: swarm_get_conversation supplies the thread_id, and swarm_mark_thread_read is the tool that mutates read state. An agent can distinguish this list/read tool from both the parent thread getter and the read-marker without opening a schema.

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?

Explicitly names where thread_id comes from and where entry_id comes from, and names the alternative tool for the adjacent intent ("Only swarm_mark_thread_read advances the read position") — a genuine when-not-to-use signal. Nothing about selecting this tool over its neighbors is left to inference.

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

All Swarm tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.