Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Wait for Space update

swarm_wait_for_space_update
Read-onlyIdempotent

While actively monitoring, wait up to 15 seconds for a newer approved Space revision. Start at 0, reuse returned revisions and read changed resources. Timeout is normal; this does not start a background listener or wake an idle host.

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": {
      "after_revision": "<after_revision>",
      "wait_ms": "<wait_ms>"
    },
    "name": "swarm_wait_for_space_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
wait_msYesMaximum wait, 0-15000 ms; timeout is normal.
space_idNoSpace ID from swarm_list_spaces; omit if sole.
after_revisionYesLast observed Space revision; initially 0.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / after_revision / description
      Added value: +"Last observed Space revision; initially 0."
    • 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 / wait_ms / description
      Added value: +"Maximum wait, 0-15000 ms; timeout is normal."
  2. Changed1 schema field changed
    • addedInput schema / properties / space_id / description
      Added value: +"Omit for a single approved Space."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare safety (readOnly, idempotent, non-destructive, closed-world). The description adds valuable behavioral context beyond that: timeout is normal and it does not start a background listener or wake an idle host, which preempts common misconceptions.

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 sentences, front-loaded with the core action, then procedural guidance, then key caveats. Every sentence is informative and none is redundant.

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 rich annotations, a full output schema, and complete parameter coverage, the description fills the remaining gaps: timeout behavior and non-background nature are called out. It stops short of explaining revision approval semantics or what 'changed resources' means in practice, but it is complete enough to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters. The description nonetheless reinforces usage semantics for after_revision ('Start at 0, reuse returned revisions') and wait_ms ('Timeout is normal'), adding meaning beyond the schema's type constraints.

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?

The description states a specific verb ('wait') and resource ('newer approved Space revision') with a clear time bound. It distinguishes itself from sibling get/list tools by its waiting semantics, though it does not explicitly name an alternative.

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 says to use this 'while actively monitoring' and gives procedural guidance: start at 0, reuse returned revisions, read changed resources. It does not name when-not-to-use or alternative tools, but the context is clear.

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