Skip to main content
Glama

serie_historica_safra

Historical crop series by season (CONAB): area, production and yield.

Instructions

Historical crop series by season (CONAB): area, production and yield.

    Products: algodao, algodao_caroco, algodao_pluma, amendoim, amendoim_1, amendoim_2, arroz, arroz_irrigado, arroz_sequeiro, aveia, cafe, cafe_arabica, cafe_conilon, cana, cana_area_total, canola, centeio, cevada, feijao, feijao_1, feijao_2, feijao_3, feijao_caupi, feijao_caupi_1, feijao_caupi_2, feijao_caupi_3, feijao_cores, feijao_cores_1, feijao_cores_2, feijao_cores_3, feijao_preto, feijao_preto_1, feijao_preto_2, feijao_preto_3, gergelim, girassol, mamona, milho, milho_1, milho_2, milho_3, soja, sorgo, trigo, triticale.

    Args:
        produto: Crop name (e.g. "soja", "milho_2")
        uf: State abbreviation (e.g. "PR"). Empty = Brazil, summed over the states.
        ano_inicio: Start year of the first season (default: 10 years ago)
    

Tool call template

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": {
      "produto": "<produto>"
    },
    "name": "serie_historica_safra"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNo
produtoYes
ano_inicioNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations, so the description carries the full burden. It discloses the source (CONAB) and the returned measures (area, production, yield), which is useful, but says nothing about permissions, rate limits, or whether the series is point-in-time vs. continuously revised.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first line, but the 44-value product dump dominates the body, and the verbatim 'Args:' docstring style is slightly raw. The list is defensible since the schema lacks an enum, but the overall shape is list-heavy rather than tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read tool with an output schema, the description covers all parameters and the critical valid-value list, so return format need not be restated. The notable gap is the absence of any routing guidance against the many sibling series tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it largely does: it enumerates 44 valid 'produto' values (absent from the schema as an enum), explains uf semantics ('Empty = Brazil, summed over the states'), and clarifies ano_inicio as the start year with a 10-years-ago default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: a historical (seasonal) crop series from CONAB returning area, production and yield. This is clearly distinguishable from data-set siblings like producao_anual and progresso_safra, though the description never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance at all: nothing says when to prefer this historical-series tool over estimativa_safra or producao_anual, and no prerequisites or exclusions are given. The Args block is parameter documentation, not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.