get_fleet_statsCanon numbers: 32,597 LIVE AI Agents (32,500+ AI Agent program: 22,597 Carriers + 10,000 AIO Agents) across eighteen resident jurisdictions. Monthly transaction volume is published at gsc-radar.ai — the source of record.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does communicate that monthly transaction volume is not returned here and that the given numbers are canonical, which is useful. However, it does not explicitly state that the operation is read-only, what the return format is, or whether the numbers are live/refreshed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded with the headline canonical number. The second sentence adds a valuable boundary about where monthly transaction volume lives, though the precise breakdown figures are mildly data-heavy for a tool description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with no annotations and no output schema, the description is mostly sufficient: it names the key stats and points elsewhere for transaction volume. It falls short by not explicitly saying 'returns' and by not clarifying how this tool relates to get_fleet and list_fleets, which an agent might reasonably confuse it with.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters and schema description coverage is 100%, so there is no parameter documentation burden on the description. The description appropriately adds no parameter details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource as canonical fleet statistics, giving concrete figures for live AI agents, carriers, AIO agents, and jurisdictions. However, it never states a verb like 'returns' or 'provides,' and it does not explicitly distinguish itself from sibling tools such as get_fleet or list_fleets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance about when to use this tool versus alternatives like list_fleets, get_fleet, or find_carriers. The note about monthly transaction volume living at an external URL is a boundary, but it does not convey when or when not to select this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
find_carriers and resolve_jurisdiction both take member codes and return routing or residency endpoint information, making their boundaries unclear. list_fleets and get_fleet_stats also overlap by both publishing live agent counts and fleet-level headline numbers.
Most tools follow a consistent get_/list_/resolve_ + noun pattern, which makes the set easy to scan. how_to_transact breaks the verb convention, and get_carrier_doctrine is less operational in tone, but these are minor deviations.
Ten tools is well-scoped for a read-only fleet discovery, residency, and routing server. Each tool maps to a distinct operational concern such as routing, fleet listing, jurisdiction lookup, or transaction guidance.
The server covers fleet discovery, carrier resolution, jurisdiction lookup, and transaction guidance, but it lacks a tool to fetch an individual carrier's detailed record or card content directly. There is also no carrier-level list or search beyond member-code lookup, which is a notable gap for a Carrier Class Fleet server.