Check whether requested community observations share compatible concepts, units, geographic boundaries, and reference periods; return explicit reasons where they do not.
| Name | Required | Description | Default |
|---|---|---|---|
| bundle | No | Comparison metric preset; defaults to municipal-economic-profile-v1. | |
| metrics | No | Optional additional fact metrics. | |
| entities | Yes | Municipality names, local slugs, or SGC codes. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool returns explicit reasons for incompatibility, which is useful. However, it does not state whether the operation is read-only, what the successful return looks like, or whether it checks pairwise or all entities at once. This leaves some ambiguity.
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 a single sentence, directly front-loaded with the action verb, and includes no filler. It efficiently conveys both what is checked and the output format.
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?
With no annotations and no output schema, the description provides the core purpose and mentions the output (explicit reasons). It does not explain the structure of those reasons or the behavior when inputs are compatible, but the schema covers parameter types. For a validation tool, this is reasonably complete.
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 already has detailed descriptions for all three parameters (100% coverage). The description adds context by linking the check criteria (concepts, units, etc.) to the requested observations, making it clear how entities and metrics are used. While it doesn't describe each parameter individually, it enhances understanding of the tool's purpose.
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 states the tool's function with the verb 'Check' and specifies the resource ('requested community observations') and the specific compatibility dimensions (concepts, units, geographic boundaries, reference periods). It also states the output (explicit reasons). This differentiates it from sibling tools like compare_communities which likely perform actual comparisons.
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 implies this is a preliminary validation step for comparison but does not explicitly state when to use it over alternatives. No exclusions or when-not-to-use guidance is provided. The sibling list suggests it should be used before compare_* tools, but this is not stated.
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.
Several tools are effectively duplicates or near-duplicates: get_emerging_signals is an explicit alias for list_economic_signals, resolve_entity and resolve_entities overlap heavily, and the markdown variants duplicate their non-markdown reports. Pairs like compare_communities/compare_municipalities and search_businesses/search_licensed_businesses also require reading long contracts to avoid misselection.
Tool names overwhelmingly follow a snake_case verb_noun pattern with sensible verbs like get_, list_, search_, and compare_. The main deviations are the backwards-compatible get_emerging_signals alias and prefix choices such as check_business_health vs get_business_health that obscure the underlying distinction.
70 tools is an extreme surface for any MCP server, far beyond the 25+ 'too many' threshold. The set is fragmented by format variants, aliases, and multiple overlapping lookup tools, making selection and maintenance costly.
The domain surface is broad: entity resolution, business health, labour, community economy, procurement, and governance evidence are all covered in depth. However, there are notable lifecycle gaps—no sandbox deletion, consent revocation, health-action cancellation, or actual exchange/connect/apply step—that leave agents with dead ends.
