Skip to main content
Glama

Fleet check: the self-check for many agents at once (free)

fleet_check
Read-onlyIdempotent

Use this when someone runs or depends on several agents: give agents (a list of up to 60 token ids, slugs or bound wallets) or owner (a wallet: the Base registrations it holds now, the 60 newest, with the total). One row per agent with its level, last payment, whether its Agent Pass holds, the Watch reading of its newest payment, open incidents, standing unlimited approvals and approvals to plain accounts, detections in 30 days, blast radius, and the items worth a look; rows with something worth a look come first. Each row is that agent's self_check in short: open it for sources and measurement times. A clean row is not a statement that the agent is safe.

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": "fleet_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerNoOr a 0x wallet: the registrations it holds
agentsNoToken ids, act_8453_N, slugs or bound wallets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, and the description adds real context beyond that: the 60-item cap, that problem rows are sorted first, how owner mode resolves registrations, and the important caveat that a clean row is not proof of safety. It does not discuss response size limits beyond the cap or timing of the underlying measurements, which is the remaining gap.

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?

Front-loaded with the trigger condition, then the parameters, then the row contents. The middle sentence is a long undifferentiated list of row fields, which is dense but all of it is load-bearing for a tool with no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the full burden of explaining return shape — and it does, enumerating the per-agent fields, the row ordering, and the interpretive caveat. Nothing an agent needs in order to call this correctly appears to be missing.

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 baseline is 3, but the description goes further: it explains that owner resolves to Base registrations the wallet holds now (60 newest plus total) and that agents accepts token ids, act_8453_N forms, slugs, or bound wallets. That adds selection semantics the schema alone does not convey.

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 capability — a batch self_check across many agents — and explicitly ties each row back to the sibling self_check, so an agent can tell fleet_check apart from self_check without opening either 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?

Gives a clear trigger condition ("use this when someone runs or depends on several agents") and points to self_check for per-row detail and sources. It stops short of stating the inverse exclusion ("for one agent, call self_check directly"), so the routing is implied rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.