stats_report_metadataRetrieves a Booksy report's period limits and available filters so you can choose valid date ranges and filters before generating the report.
What a report needs: its period limits and available filters.
| Name | Required | Description | Default |
|---|---|---|---|
| fresh | No | Skip the local cache | |
| report | Yes | Report key |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructiveness, so the safety profile is covered. The description adds that the result contains period limits and available filters, but it does not disclose caching behavior or the meaning of the 'fresh' parameter.
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 compact sentence with no wasted language. Its brevity is efficient, though the phrasing is somewhat fragmented rather than front-loaded with a clear action.
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 simple two-parameter metadata tool with rich annotations, the description is minimally adequate: it indicates that period limits and filters are returned. However, without an output schema, it should more clearly describe the returned metadata and the role of the 'fresh' cache flag.
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?
Schema description coverage is 100%, so both 'report' and 'fresh' are documented in the schema. The description does not add meaning to either parameter; per the high-coverage baseline, a 3 is appropriate.
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 gestures at report metadata by mentioning 'period limits and available filters,' but it has no clear action verb and does not distinguish this tool from siblings such as stats_report_catalog or stats_report. An agent can infer it is a metadata lookup, but only vaguely.
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 on when to use this tool versus stats_report_catalog, stats_report, or stats_report_section. The description implies it is a preparatory lookup but never states that or names alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.