Skip to main content
Glama

Whole-fleet location sweep

fleet_status

Sweep all catalog providers with known API hosts to return a single table summarizing publisher, serving entity, edge operator, region, precision, and confidence per lane.

Instructions

Run locate_model across every catalog provider that has a known API host and return one summary table: publisher, serving entity, edge operator, country/region, precision and confidence per lane. The one call to re-run whenever the fleet or a provider changes.

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

Input Schema

NameRequiredDescriptionDefault
deepNoInclude PeeringDB facility lookups (slower, more evidence).
lanesNoOptional filter: lane/CLI names or provider keys.
limitNoMax providers to sweep (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden. It usefully reveals the fan-out behavior (iterating every provider with a known API host) and that the result is a single consolidated table, but it says nothing about cost or latency of a wide sweep, failure behavior when a provider is unreachable, or whether any state is mutated. The schema note that deep is 'slower, more evidence' is the only performance hint.

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?

Two sentences, front-loaded with the action and output shape, then the usage cue. Every clause carries information and nothing is repeated from the schema.

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?

For a read-only fan-out tool with no output schema, the description does the necessary work by naming the returned columns (publisher, serving entity, edge operator, country/region, precision, confidence). A note on expected latency or partial-failure handling for a multi-provider sweep would make it fully complete.

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 100%, so deep, lanes, and limit are already documented in the input schema, including the default of 10 and the max of 20. The description adds no syntax, default, or interaction detail beyond that, so it sits at the baseline.

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 concrete verb and resource ('Run locate_model across every catalog provider... return one summary table') and enumerates the returned columns, so the agent knows this is a fleet-wide aggregation rather than a single lookup. It also implicitly separates itself from the sibling locate_model, which is described as the per-provider primitive this tool fans out.

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?

The closing sentence ('The one call to re-run whenever the fleet or a provider changes') gives a clear triggering condition for use. It does not state when to prefer a narrower sibling such as find_regional_endpoints or locate_model directly, so exclusions are left to inference.

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