Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

List Schedules

swarm_list_schedules
Read-onlyIdempotent

Browse schedules; active_only selects enabled ones. Read triggers with swarm_get_schedule, outcomes with swarm_list_runs. Creates no occurrences.

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

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.
active_onlyNoTrue filters to enabled records.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / active_only / description
      Previous value: -"Return only enabled records when true."New value: +"True filters to enabled records."
    • 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. Changed5 schema fields changed
    • addedInput schema / properties / active_only / description
      Added value: +"Return only enabled records when true."
    • 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.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds a real behavioral fact beyond them: "Creates no occurrences," clarifying that listing does not materialize schedule instances. It does not address pagination semantics or result volume, but the schema already covers cursor/limit 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 clauses, front-loaded with the verb+resource, then the filter hint, then sibling routing. No filler and nothing restated from annotations.

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, return values need no explanation, and pagination is fully documented in the schema. Only the absence of guidance on combining filters or on cross-page consistency keeps it from a 5, and that is a minor gap.

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% and each parameter already carries a descriptive note, so the baseline is 3. The description's only parameter content, "active_only selects enabled ones," duplicates the schema wording ("True filters to enabled records") without adding syntax, defaults or interaction rules.

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?

States a specific verb and resource ("Browse schedules") with a scoping modifier (active_only selects enabled ones), and explicitly distinguishes itself from swarm_get_schedule (triggers) and swarm_list_runs (outcomes). An agent can separate this from its siblings 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternatives and the axis on which to choose them (triggers vs. outcomes), which is stronger than most. It stops short of stating when listing is preferable to fetching, or when to combine with space_id/active_only filtering, so not a full 5.

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