Swarm

Get Space answer

swarm_get_answer

Read-onlyIdempotent

Read a saved answer's rationale and sources using answer_id from swarm_list_answers. This creates no question or learning work; submitting a new answer request requires separate write permission.

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": {
      "answer_id": "<answer_id>"
    },
    "name": "swarm_get_answer"
  }
}

Input Schema

Name	Required	Description	Default
`space_id`	No	Space ID from swarm_list_spaces; omit if sole.
`answer_id`	Yes	Saved answer ID from swarm_list_answers.

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 / answer_id / description

Previous value: -"Saved answer ID returned by swarm_list_answers or swarm_ask_space."New value: +"Saved answer ID from swarm_list_answers."

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

Changed2 schema fields changedOct 29, 2026
- addedInput schema / properties / answer_id / description
```
Added value: +"Saved answer ID returned by swarm_list_answers or swarm_ask_space."
```
- addedInput schema / properties / space_id / description
```
Added value: +"Omit for a single approved Space."
```
First observedOct 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already specify readOnlyHint and idempotentHint, so the read-only nature is covered. The description adds useful context beyond that: no question/learning work is created and write actions require a separate permission, which helps the agent understand side-effect and authorization boundaries.

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?

Two compact sentences with the read action and its ID source front-loaded, followed by a clarifying non-side-effect note. No waste or redundancy.

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 simple two-parameter read with rich annotations and an output schema, this is nearly complete. The output schema covers return values, so the description needn't explain them; only explicit sibling differentiation is missing.

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%, so both parameters are documented in the schema, including space_id's omit-if-sole rule. The description reinforces answer_id provenance but adds nothing about syntax or format beyond the schema, matching the baseline 3.

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 and resource: read a saved answer's rationale and sources. It also names swarm_list_answers as the source of answer_id, orienting the agent. It does not explicitly distinguish this from the near-identical sibling swarm_get_answer_contract, which keeps it below a 5.

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?

Clear trigger: use the answer_id obtained from swarm_list_answers. It also draws a boundary by stating this creates no question or learning work and that submitting a new answer needs separate write permission, implying this is not the tool for writes. No explicit mention of the sibling alternatives though.

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.