Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

List Space operations

swarm_list_operations
Read-onlyIdempotent

Browse submitted intelligence operations by kind, capability or status; inspect results with swarm_get_operation. Discover kinds with swarm_list_capabilities. No work is submitted or retried.

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_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size; follow next_cursor for more.
orderNoasc or desc; retain the same order across pages.
cursorNoPrevious next_cursor; keep filters and order.
statusNoStatus filter; use values returned for this resource.
space_idNoSpace ID from swarm_list_spaces; omit if sole.
capability_keyNoCapability filter from swarm_list_capabilities.
operation_kindNoKind from swarm_list_capabilities; read its operation contract.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / capability_key / description
      Added value: +"Capability filter from swarm_list_capabilities."
    • 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."
    • addedInput schema / properties / operation_kind / description
      Added value: +"Kind from swarm_list_capabilities; read its operation contract."
    • 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 / status / description
      Added value: +"Status filter; use values returned for this resource."
  2. Changed4 schema fields changed
    • 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."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the description's job is narrower. It reinforces the safety profile in domain terms ('No work is submitted or retried'), which is genuinely useful against siblings that do submit work, but it adds little else beyond the annotations.

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 compact clauses, front-loaded with what it lists, then the follow-up route, then the negative safety statement. Every sentence carries information and nothing is repeated.

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 and all seven parameters optional and documented, the description does what it must: scope, routing, and safety. The one gap is that it never mentions space scoping, even though the title says 'Space operations' and space_id is the main scoping input, which could leave an agent unsure whether results are space-bounded.

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 100% with per-parameter descriptions that already document paging via next_cursor, ordering, and where filter values come from. The description echoes the kind/capability/status filter axes but adds no syntax or format 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?

Specific verb ('Browse') plus a precisely scoped resource ('submitted intelligence operations') and the three filter axes (kind, capability, status). It also names the sibling for follow-up (swarm_get_operation) and for discovery (swarm_list_capabilities), so an agent can place it in the tool graph 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 routes the agent: use swarm_get_operation to inspect a result, swarm_list_capabilities to discover valid kinds. The closing clause 'No work is submitted or retried' clarifies when this tool is the wrong choice for anything that kicks off work, which is the main ambiguity for a 'swarm' tool family.

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

All Swarm toolsInspect
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.

Resources