Skip to main content
Glama

Read quota across swarm backends

swarm_quota
Read-only

Read available quota and usage information from CodeBuddy, Qoder, ZCode, or all backends to monitor remaining capacity, refresh data, and filter usage by recent days.

Instructions

Read available quota/usage information from CodeBuddy, Qoder, ZCode UI, or all (all).

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

Input Schema

NameRequiredDescriptionDefault
backendNo
refreshNo
sinceDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external reach are covered. The description adds nothing further: it does not say whether `refresh` forces live network calls, whether results are cached or how stale they may be, or what latency to expect from a multi-backend fan-out.

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, and the backend list sits at the end where it belongs. It is efficient, though its brevity reflects under-specification rather than deliberate economy.

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?

There are three parameters at 0% schema description coverage, no output schema, and no explanation of aggregate-vs-single-backend behavior. An agent can make the call, but must guess at the semantics of `refresh` and `sinceDays` and at whether the result shape differs per backend.

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 description coverage is 0%, so the description carries the burden, and it only partially does so by naming backend values (though "ZCode UI"/"Qoder" differ slightly from the enum values `zcode`/`qoder`). `refresh` and `sinceDays` (1-90) are given no meaning at all in the description.

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 pairs the verb "Read" with a specific resource, "available quota/usage information," and enumerates the backends it can pull from, including the aggregate `all` option. It is clear what the tool returns, though it never explains how it relates to the more specific sibling tools like zcode_quota or codebuddy_usage.

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

Usage Guidelines2/5

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

There is no guidance on when to call this aggregator versus the per-backend siblings (zcode_quota, codebuddy_usage), nor any stated preconditions. The only routing signal is the enumerated backend values, which is usage context implied by the parameter rather than explicit guidance.

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