Zwraca słownik partii politycznych w Polsce wraz z progami wyborczymi (5% partia, 8% koalicja), informacją o statusie koalicji, kolorami i slugami.
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": "get_parties"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 burden. It does disclose the shape of the returned data (thresholds, coalition status, colors, slugs), which is useful, but says nothing about whether the data is static or live, its scope (current parliamentary parties only?), or any caching/auth behavior.
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 states the resource and its contents with zero filler. Every listed item (thresholds, coalition status, colors, slugs) corresponds to actual returned fields.
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 zero-parameter reference lookup with no output schema, the description usefully enumerates the returned fields, which is what an agent needs to know. It is nearly complete; only the data's scope/currency is unstated.
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 tool takes zero parameters, so the baseline is 4. The description correctly implies no filtering arguments are needed — the whole dictionary is returned — and requires no further parameter explanation.
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?
States a specific verb and resource ('Zwraca słownik partii politycznych w Polsce') and enumerates the payload (electoral thresholds, coalition status, colors, slugs). This clearly separates it from siblings like get_pollsters, get_surveys and get_political_events, which cover different resources.
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 lookup nature is implied by the description — it is a static reference of parties — but there is no explicit statement of when to call it versus alternatives such as get_polling_averages or get_seat_projections (e.g. as a slug/color lookup before rendering results). Usage is inferable rather than stated.
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.