Swarm

Get Space operation

swarm_get_operation

Read-onlyIdempotent

Inspect a submitted intelligence operation's saved status and result. Find IDs with swarm_list_operations. No work is submitted or rerun; result references retain their read restrictions.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "swarm_get_operation"
  }
}

Input Schema

Name	Required	Description	Default
`space_id`	No	Space ID from swarm_list_spaces; omit if sole.
`operation_id`	Yes	Operation ID from swarm_list_operations.

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

Previous value: -"Operation ID returned by swarm_list_operations or a submitted operation."New value: +"Operation ID from swarm_list_operations."

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 / operation_id / description
```
Added value: +"Operation ID returned by swarm_list_operations or a submitted operation."
```
- addedInput schema / properties / space_id / description
```
Added value: +"Omit for a single approved Space."
```
First observedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is structured. The description adds genuinely non-redundant context beyond that: no work is submitted or rerun on inspection, and result references retain their read restrictions, which tells the agent to expect access-control behavior on returned data.

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?

Three short sentences, with the core purpose front-loaded and the ID-discovery hint and non-mutation caveat following in priority order. No filler, though the middle pointer sentence sits slightly awkwardly before the behavioral clause for readers scanning for constraints.

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 an output schema present, the description needn't enumerate return fields, and it still covers the key agent concerns: where the ID comes from, that nothing is mutated, and that results are access-restricted. What's missing is minor—there is no mention of behavior for an unknown or not-yet-complete operation ID.

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 both parameters carry descriptions pointing at swarm_list_spaces and swarm_list_operations as sources. The description itself only restates where operation IDs come from and adds no format or optionality detail 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Inspect a submitted intelligence operation's saved status and result" gives a specific verb (inspect) and resource (operation) with an explicit scope: saved status and result of a submitted operation. It contrasts cleanly with the sibling swarm_list_operations, which is an enumeration tool rather than a fetch-by-ID tool.

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?

It routes the agent to swarm_list_operations for ID discovery, and states what this tool does not do ("No work is submitted or rerun"), which is exactly the confusion an agent might have between inspecting and re-executing an operation. Both the when and the when-not are present.

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.