Swarm

List Space answers

swarm_list_answers

Read-onlyIdempotent

Browse saved answers by visibility or confidence. Inspect rationale and sources with swarm_get_answer. This creates no new question or learning work.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`limit`	No	Page size; follow next_cursor for more.
`order`	No	asc or desc; retain the same order across pages.
`cursor`	No	Previous next_cursor; keep filters and order.
`space_id`	No	Space ID from swarm_list_spaces; omit if sole.
`confidence`	No	Confidence using this tool's numeric or enum schema.
`visibility`	No	working (default), hidden or all; normal read access applies.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026

addedInput schema / properties / confidence / description

Added value: +"Confidence using this tool's numeric or enum schema."

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."

changedInput schema / properties / order / description

Previous value: -"Paging order."New value: +"asc or desc; retain the same order across pages."

changedInput schema / properties / space_id / description

Previous value: -"Omit for a single approved Space."New value: +"Space ID from swarm_list_spaces; omit if sole."

addedInput schema / properties / visibility / description

Added value: +"working (default), hidden or all; normal read access applies."

Changed4 schema fields changedOct 29, 2026
- addedInput schema / properties / cursor / description
```
Added value: +"Previous next_cursor; same filters and order."
```
- addedInput schema / properties / limit / description
```
Added value: +"Page size."
```
- addedInput schema / properties / order / description
```
Added value: +"Paging order."
```
- addedInput schema / properties / space_id / description
```
Added value: +"Omit for a single approved Space."
```
First observedOct 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The sentence 'This creates no new question or learning work' adds mild reinforcement but no new information; return/pagination behavior is in the schema and output schema.

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 sentences, front-loaded with the action and filters, followed by the alternative and the read-only reassurance. No waste.

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?

With annotations covering safety, a full parameter schema, and an output schema, the description is sufficient for correct invocation. It could have noted pagination or the space scoping relationship with swarm_list_spaces, but the essentials are present.

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 description coverage is 100% and each parameter is already documented (limit/next_cursor, order stability, cursor reuse, space_id source, visibility values). The description adds no parameter semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Browse') and resource ('saved answers') with the filterable axes (visibility, confidence). It also names the sibling swarm_get_answer as the detail path, though it does not explicitly say 'this is the list counterpart' to get_answer.

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?

Routes the agent: use swarm_get_answer to inspect rationale and sources, implying this tool is for enumeration and that one should switch for detail. Lacks explicit when-not guidance (e.g., when to use list vs other list siblings), but the alternative is named with a condition.

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.