Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Get Run

swarm_get_run
Read-onlyIdempotent

Inspect a Run's status, requirements and lineage before acting. Get IDs with swarm_list_runs and inputs with swarm_get_run_context. No lease or execution starts.

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": {
      "run_id": "<run_id>"
    },
    "name": "swarm_get_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesRun ID from swarm_list_runs.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / run_id / description
      Previous value: -"ID from launch or swarm_list_runs."New value: +"Run ID from swarm_list_runs."
  2. Changed1 schema field changed
    • addedInput schema / properties / run_id / description
      Added value: +"ID from launch or swarm_list_runs."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context by stating that no lease or execution is started, which goes beyond the annotations' safety flags, but it does not discuss auth or error behavior.

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 tool's purpose and followed by actionable routing details. There is no wasted text.

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

Completeness5/5

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

With a complete input schema, an output schema, and rich annotations, the description supplies the remaining needed context: what is inspected, where IDs and inputs come from, and that no execution starts.

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?

The single run_id parameter has 100% schema description coverage and explicitly says it comes from swarm_list_runs. The description reinforces that source but adds no additional format, validation, or semantic detail beyond 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?

The description uses a specific verb (Inspect) and resource (Run) and scopes the result to status, requirements, and lineage. It also distinguishes the tool from swarm_list_runs and swarm_get_run_context, so an agent can identify its role without opening schemas.

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?

It clearly says to inspect a Run before acting, points to swarm_list_runs for IDs, and routes input lookup to swarm_get_run_context. The clause 'No lease or execution starts' also clarifies that this is not an execution tool, though it does not enumerate every sibling alternative.

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