Skip to main content
Glama

combustiveis_precos

Read-onlyIdempotent

Retrieve official ANP monthly fuel consumer prices by product, state, and municipality to rank state and municipal averages and list lower-priced stations.

Instructions

Preço de combustíveis ao consumidor nos postos (ANP, levantamento mensal).

Sem UF: média nacional e ranking por UF (mais barato primeiro). Com UF: ranking dos municípios. Com UF e município: os postos mais baratos. Produtos: gasolina, gasolina_aditivada, etanol, diesel (S500), diesel_s10, gnv, glp. Sem ano e mês, usa o último mês publicado. Os valores são médias simples das coletas, sem ponderar pelo volume vendido. Para uma série mensal da média nacional, use os indicadores de combustíveis do catálogo.

Tool call template

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": "combustiveis_precos"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNo
anoNo
mesNo
limiteNo
produtoNogasolina
bandeiraNo
municipioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. Beyond that, the description discloses two things the structured data cannot: the default temporal behavior ('Sem ano e mês, usa o último mês publicado') and the aggregation semantics ('médias simples das coletas, sem ponderar pelo volume vendido'), plus the sort order of results (cheapest first) — all material to correct interpretation.

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

Conciseness4/5

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

Front-loaded with the resource, then layered by granularity, then defaults and caveats — a logical order with little waste. Slightly dense in the product enumeration, but each clause carries information an agent needs.

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

Completeness4/5

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

For a seven-parameter, no-output-schema tool, the definition covers input hierarchy, defaults, units of aggregation, and result ordering well. The gaps are the undocumented 'limite' and 'bandeira' parameters and the absence of any note on the return payload's shape, which matters somewhat more given there is no output schema.

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

Parameters3/5

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

With 0% schema description coverage, the description must carry the load, and it does cover the substantive ones: the uf/municipio hierarchy, ano/mes defaulting, and the full allowed product vocabulary. However, 'limite' (default 10) and 'bandeira' are never mentioned anywhere, leaving two of seven parameters with no semantics at all, and the expected format of uf/municipio strings is not stated.

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

Purpose5/5

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

Names a concrete resource and scope: consumer fuel prices at stations from ANP's monthly survey. It also spells out what the result set becomes at each geographic granularity (national average + UF ranking, municipality ranking, cheapest stations), so an agent knows exactly what it gets without opening the schema.

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

Usage Guidelines4/5

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

Gives explicit routing guidance for the main ambiguity — 'Sem UF' vs 'Com UF' vs 'Com UF e município' — and points away from itself for monthly national series ('use os indicadores de combustíveis do catálogo'). The alternative is described rather than named as a concrete sibling tool, so the agent must still map it to the catalog itself; there is no explicit when-not-to-use beyond that.

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