Side income of all members of the Bundestag: ranking and totals per party, filter by party, category and minimum amount.
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": "list_side_income"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| party | No | ||
| min_eur | No | ||
| category | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the output shape (ranking and totals) but says nothing about permissions, whether results are read-only, pagination/limit behavior, or ordering semantics for a 4-parameter query 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?
A single front-loaded sentence states the resource first and the filters second, with no wasted words. It is dense but appropriately sized for the tool's simplicity.
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, no output schema, and 0% schema coverage across 4 params, the definition should do more. It omits the limit parameter, pagination behavior, and any ordering/format detail, leaving the agent to guess on key invocation aspects.
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%, so the description must compensate. It clarifies party, category, and 'minimum amount' (min_eur), adding real meaning over the bare schema, but it never mentions the limit parameter or value formats/units, leaving one of four params undocumented.
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 names the specific resource (side income of all Bundestag members) and states what the tool produces (ranking and totals per party), which implicitly separates it from the single-member sibling get_member_side_income. It is clear but never explicitly names or contrasts with that sibling.
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 when-to-use guidance, no prerequisites, and no mention of alternatives such as get_member_side_income for a single member. The filter clause describes parameters, not usage conditions.
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.