Skip to main content
Glama

List available swarm backends and live health

swarm_backends
Read-only

Inspect registered subagent CLI and UI backends to check availability, supported models, profiles, and active versus maximum concurrency before routing tasks.

Instructions

Inspect registered subagent CLI/UI backends (codebuddy, qoder, zcode), their availability, supported models, profiles, and active/max concurrency.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the listing reflects registered backends plus 'availability' and 'active/max concurrency', implying a live-ish snapshot, but it never clarifies whether health is probed at call time, whether results are cached, or how stale the concurrency numbers may be. Useful context, but the 'live health' claim in the title is only partially substantiated in the body.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every element in the enumeration (backends, availability, models, profiles, concurrency) tells the agent something about the payload. The dense comma list is slightly harder to scan than a short bulleted structure would be, but nothing 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 no output schema and no parameters, the description carries the burden of describing return content, and it does so by enumerating the fields the agent will get back. What is missing is any indication of response shape or ordering, and clarification of what 'availability' means concretely. For a zero-arg read-only inventory tool this is close to sufficient.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. No misleading parameter hints are present.

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?

Uses a specific verb ('Inspect') and a precisely bounded resource ('registered subagent CLI/UI backends'), even naming the concrete backend families (codebuddy, qoder, zcode) and the attributes surfaced. This makes it clearly a discovery/inventory tool rather than a runner. It stops short of naming which sibling to use instead (e.g. swarm_list, zcode_list, swarm_quota), so differentiation is inferential rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named. However, the framing around availability, supported models, and concurrency makes the implied use case (pre-flight capability/health check before dispatching work) reasonably evident to an agent. Adequate but leaves routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.