Participant facet stats
Global participant facet counts (per country/scheme/smp/ap/doctype/transport_profile, registered share, provenance split) plus an estimated total, from the hourly rollup. Keyless-cacheable — safe for the marketing site to hit directly.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description adds significant behavioral context: 'Keyless-cacheable' indicates no auth and cacheability, 'hourly rollup' implies data freshness and potential lag, and 'estimated total' warns of approximation. This goes well beyond the annotation.
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 extremely tight and front-loaded: a short title followed by one dense sentence covering output dimensions, data source, freshness, and usage safety. Every word adds value, with no redundancy.
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 output schema, the description covers the response contents (facet counts, estimated total), the data source (hourly rollup), and the access context (keyless-cacheable). It gives a complete picture of what to expect and how to use it.
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 tool has zero parameters, so the schema coverage is effectively complete. The description adds no parameter details but doesn't need to; instead, it explains the scope of the fixed output. This aligns with the baseline of 4 for no-parameter tools.
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 explains the tool provides global participant facet counts across multiple dimensions (country/scheme/smp/ap/doctype/transport_profile) plus an estimated total. It effectively distinguishes the current snapshot nature from historical tools by mentioning 'hourly rollup', though it lacks an explicit verb like 'retrieve' or 'list' and doesn't directly compare against siblings.
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?
The description gives a concrete usage context: 'safe for the marketing site to hit directly' implying it is cacheable and requires no authentication. However, it doesn't explicitly state when to prefer this over sibling tools like get_participant_stats_history, nor does it provide exclusions or alternative guidance.
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.
Most tools are cleanly separated by resource type: participants, access points, hosts, providers, incidents, anomalies, and SLA each have their own get/list vocabulary. The main ambiguous pairs are get_provider_sla vs get_provider_sla_by_key, list_providers vs list_public_providers, and get_summary vs get_network_summary.
The overall get_/list_ verb_noun pattern is consistent and readable, and plural/singular resource names are mostly clear. There are a few exceptions: get_provider_sla and get_country_providers return collections despite using get_, and list_provider_certs is more of an aggregate posture endpoint than a simple list.
43 tools is well beyond the typical well-scoped MCP surface and will make the tool set harder for an agent to navigate defensibly. The tools are systematically grouped, but this looks like a broad REST API surface rather than a compact, purpose-fit MCP server.
For a read-only monitoring and directory domain, the coverage is unusually complete: list/detail endpoints, histories, SLA tables, churn breakdowns, anomalies, incidents, adoption aggregates, software landscape, and quality checks are all represented. The drill-down routes such as churn totals to churn participants also avoid dead ends.
