Fetch structured FAOSTAT report data to answer questions about global food and agriculture statistics, including crop production, trade, food security, and emissions.
Get structured report data from FAOSTAT.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | en | |
| payload | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: only "Get" implies a read operation. There is no mention of authentication, pagination, rate limits, response size, or what the opaque required payload does.
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?
It is a single sentence, but the brevity reflects under-specification rather than efficient front-loading. Nothing is wasted, yet nothing useful is delivered.
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?
Although an output schema exists (so return values need not be described), the combination of zero annotations, an opaque required nested payload, and no usage guidance makes this definition inadequate for correct invocation. An agent has no basis for constructing the payload.
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 required "payload" parameter is an unconstrained object with additionalProperties=true. The description adds no meaning whatsoever about what belongs in payload or how "lang" affects results, leaving the primary input completely 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 a verb ("Get") and a resource ("structured report data from FAOSTAT"), but "structured report data" is vague and overlaps heavily with siblings like faostat_get_data, faostat_get_report_headers, and faostat_get_metadata. An agent cannot tell from this text which of those it should call.
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 on when to use this tool versus the many sibling retrieval tools, and no prerequisites or context are given. The agent is left to infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.