list_groups_reportsLists group reports, optionally filtered by backup, restore, migration, or bulk_import type, to review operation history and manage data exports.
Get All
| Name | Required | Description | Default |
|---|---|---|---|
| report_type | No | ||
| accept-language | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.20.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get All' says nothing about scope, pagination, filtering, permissions, side effects, or return behavior—leaving the agent to guess.
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 short, but this is under-specification rather than effective conciseness. No sentence earns its place because the two words add no useful operational information.
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?
Despite having an output schema, the tool description lacks any semantic context about what resource is returned, what the report_type filter does, or how to select this tool among many report-related siblings. The description is wholly inadequate for a tool with parameters and an output schema.
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 0%, and the description provides no explanation of report_type or accept-language. The agent cannot infer the meaning or effect of these parameters from 'Get All'; the description completely fails to compensate for the missing schema descriptions.
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 'Get All' is a bare placeholder that effectively restates the tool's name/title without specifying the resource or any distinguishing detail. It gives no indication that this endpoint lists group reports or how it differs from related report tools.
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 guidance about when to use this tool versus alternatives like get_groups_reports_by_item or delete_groups_reports_by_item. The phrase 'Get All' only weakly implies bulk retrieval, but provides no context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.