Save a report filter to reuse in BeezUP reports, enabling consistent data views.
Save the report filter
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "SaveReportFilter"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Request body |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It states 'Save' implying a write operation but does not mention idempotency, authorization requirements, rate limits, or any side effects. This is insufficient for a mutation tool.
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 short sentence, which is concise but lacks any structuring or additional information. It conveys the basic purpose but does not add value beyond the tool's name.
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 save tool with one complex parameter and no output schema, the description is incomplete. It does not explain the effect on existing filters, conflict behavior, response format, or error conditions. Without annotations, more detail is needed.
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 only parameter 'body' is described as 'Request body', which adds no useful meaning beyond the schema's type. The schema's description coverage is 100% but the description is generic and does not explain the structure or required fields of the nested object.
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 'Save the report filter' indicates persistence of a report filter, but it does not clarify whether this creates a new filter or updates an existing one. The verb is ambiguous, and there is no distinction from potential sibling tools like UpdateReportFilter or CreateReportFilter.
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?
No guidance is provided on when to use this tool versus alternatives. The sibling list includes many other tools, but there is no mention of when to choose SaveReportFilter over GetReportFilter, DeleteReportFilter, or other save/update tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.