Retrieve aggregate event statistics from a local cache, including counts by status, year, and top cities for an organization. Get quick insights without API calls.
Retrieve aggregate event statistics (events count by status, by year, and by top cities) from local SQLite cache.
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| organization_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does disclose a meaningful behavioral trait—reading from a local SQLite cache, which signals potential staleness and no network dependency. But it does not state what happens when the cache is empty, whether sync_organization_events must be run first, or how freshness is maintained.
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?
A single front-loaded sentence that delivers verb, resource, output dimensions, and data source with zero filler. Every phrase earns its place and the key differentiator (cache) appears early.
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?
The output schema covers return values, and the core purpose is clear, so the definition is adequate. However, an agent still lacks guidance on cache freshness versus live endpoints, prerequisites (e.g., whether the cache must be synced), and parameter semantics—moderate gaps for a tool with no annotations and no parameter documentation.
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?
With 0% schema description coverage, the description must compensate, but it only alludes to 'by year' without clarifying whether the year parameter filters or groups results (the description says stats are grouped 'by year' while year is also an input). It says nothing about organization_id scoping, so the agent is left guessing about both parameters.
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 states a specific verb and resource ('Retrieve aggregate event statistics') from a distinct source ('local SQLite cache'), and enumerates the exact breakdowns (by status, by year, by top cities). This clearly differentiates it from siblings like get_sales_report, get_attendees_report, and list_organization_events.
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 phrase 'from local SQLite cache' implies a tradeoff against live-reporting siblings (get_sales_report, get_attendees_report, search_events), suggesting the cached variant is for fast/offline reads. However, it never names alternatives or states when to prefer the cache versus when fresh data is required, so the usage context is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.