Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Get Task

swarm_get_task
Read-onlyIdempotent

Read a Task's instructions and executor requirements before launch. Get IDs with swarm_list_tasks. No Run is started.

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": {
      "task_id": "<task_id>"
    },
    "name": "swarm_get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID from swarm_list_tasks.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / task_id / description
      Previous value: -"ID from swarm_list_tasks or swarm_create_task."New value: +"Task ID from swarm_list_tasks."
  2. Changed1 schema field changed
    • addedInput schema / properties / task_id / description
      Added value: +"ID from swarm_list_tasks or swarm_create_task."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds a domain-specific side-effect claim that reading does not initiate a Run. Return shape is handled by the output schema. It does not discuss permissions or failure modes, keeping it short of a 5.

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 that front-load the purpose, then the prerequisite, then the side-effect clarification. Nothing is padded and every sentence carries distinct information.

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 single-parameter read tool with full annotations and an output schema, the description covers purpose, prerequisite, and side effects. Only minor gaps remain, such as error behaviour on an unknown task_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?

Only one parameter and schema coverage is 100%, with the schema description itself pointing at swarm_list_tasks. The description's mention of getting IDs matches but does not extend the schema's own wording, so 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 (read) and resource (Task) and names the fields returned: instructions and executor requirements. It also carves out scope against a launch operation ("No Run is started"), though it doesn't distinguish itself from any of the many other swarm_get_* siblings by name.

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?

Gives a clear usage context ("before launch") and a prerequisite workflow ("Get IDs with swarm_list_tasks"), which is exactly the routing an agent needs. It stops short of explicit when-not conditions or naming an alternative getter to use instead.

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