World or regional GDP nowcast with coverage and each economy's contribution (pp).
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"aggregate": "<aggregate>"
},
"name": "get_aggregate"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| quarter | No | ||
| aggregate | Yes |
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 disclosure burden. It does usefully disclose output content (coverage plus contributions in percentage points), which is valuable given there is no output schema, but it says nothing about data vintage/freshness, units beyond 'pp', or whether the call is a pure read.
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 compact sentence with the scope and return content front-loaded and no wasted words. It is terse to the point of under-specification, but that is a completeness issue rather than a structural one.
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 two-parameter read tool with no output schema, the description gives a partial picture of the return payload, which helps. However it omits the meaning/format of 'quarter', the required aggregate semantics, and any indication of data currency, so an agent could still invoke it incorrectly.
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 only loosely gestures at the 'aggregate' parameter via 'World or regional' — it never mentions the required aggregate argument explicitly or the optional 'quarter' parameter. The enum values and quarter format are left undocumented in both the schema and prose.
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 a specific resource (GDP nowcast) and scope (world or regional aggregates) plus what the result contains (coverage, per-economy contributions in pp). The verb is implicit in the name 'get_aggregate', but the domain is unambiguous and it is distinguishable from an economy-level nowcast tool.
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 on when to choose this over the sibling get_nowcast, nor on required inputs or time-scope behavior. The word 'aggregate' implies the difference, but that inference is left entirely to the agent.
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.