Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

List Tasks

swarm_list_tasks
Read-onlyIdempotent

Browse saved Task briefs; inspect one with swarm_get_task. Launching requires separate permission.

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

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.
space_idNoSpace ID from swarm_list_spaces; omit if sole.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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."
    • 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."
  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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the useful context that launching requires separate permission, but it does not describe return format, pagination behavior, or rate limits beyond what is in the schema.

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 sentences, front-loaded with the core purpose, zero waste. Every clause adds value: the browse action, the pointer to swarm_get_task, and the permission caveat.

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?

Given a simple list tool with a fully described schema and an output schema, the description covers purpose, alternative, and a key constraint. It could mention pagination or the returned briefs' structure, but those are already handled by the schema and output schema, making the definition nearly complete.

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%, so all four parameters (limit, order, cursor, space_id) are already documented in the schema. The description adds no parameter-specific meaning, which is acceptable given the high coverage — 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?

The description uses a specific verb (browse) and resource (saved Task briefs), and explicitly distinguishes the tool from swarm_get_task by naming it as the way to inspect a single task. An agent can immediately tell this is the list operation for tasks.

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 names the alternative for detail inspection (swarm_get_task) and adds a permission constraint for launching. However, it does not explicitly state when-not to use this list (e.g., when you already have an ID) or how it differs from other list tools, so it falls slightly short of full when/when-not guidance.

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