Skip to main content
Glama
Mestre Prático & NutriPreço Official MCP Server

Mestre Prático & NutriPreço Official MCP Server

brazil_fuel_prices

Read-onlyIdempotent

Query real-time audited fuel prices in Brazil by state, city, and fuel type from ANP data to compare or rank stations.

Instructions

Queries real-time audited retail fuel prices in Brazil (Regular Gasoline, Additive Gasoline, Hydrous Ethanol, Diesel S10, and CNG) sourced from Brazil's National Petroleum Agency (ANP) across 4,750+ stations in all 27 states and 417+ cities. Updated weekly with daily SEFAZ NFC-e cross-validation. Read-only operation; no authentication required for standard rate limits (60 req/min, max 50 stations returned per call). Use brazil_list_states first to discover valid state codes (uf), or brazil_compare_regions to compare averages between two states.

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": {
      "uf": "<uf>"
    },
    "name": "brazil_fuel_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufYesTwo-letter Brazilian state code in lowercase (e.g., 'sp', 'rj', 'mg', 'ba', 'pr', 'ce', 'df'). Call brazil_list_states for all 27 valid UF codes.
cidadeNoOptional city name or URL slug (e.g., 'sao-paulo', 'rio-de-janeiro', 'cabo-frio', 'curitiba'). Omit to retrieve statewide summary.
combustivelNoFuel type filter for price ranking (default: 'todos').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / cidade / description
      Previous value: -"Nome ou slug da cidade (ex: 'sao-paulo', 'rio-de-janeiro', 'cabo-frio', 'curitiba')"New value: +"Optional city name or URL slug (e.g., 'sao-paulo', 'rio-de-janeiro', 'cabo-frio', 'curitiba'). Omit to retrieve statewide summary."
    • changedInput schema / properties / combustivel / description
      Previous value: -"Tipo de combustível para ranking"New value: +"Fuel type filter for price ranking (default: 'todos')."
    • changedInput schema / properties / uf / description
      Previous value: -"Sigla do estado brasileiro em minúsculo (ex: 'sp', 'rj', 'mg', 'ba', 'pr', 'ce', 'df')"New value: +"Two-letter Brazilian state code in lowercase (e.g., 'sp', 'rj', 'mg', 'ba', 'pr', 'ce', 'df'). Call brazil_list_states for all 27 valid UF codes."
  2. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing operational constraints an agent cannot infer: 60 req/min rate limit, a hard cap of 50 stations returned per call, weekly refresh cadence, SEFAZ NFC-e cross-validation, and that no authentication is needed at standard limits. The readOnlyHint/idempotentHint annotations only cover the safety profile, so this added context is genuinely valuable.

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?

Strongly front-loaded: the core action and resource come first, then coverage scope, then constraints, then routing guidance. It is dense—three long sentences packed with stats—but essentially every clause carries decision-relevant information, with only minor density cost.

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

Completeness5/5

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

For a read-only, three-parameter tool with no output schema, this covers everything needed to invoke it correctly: prerequisites, valid code discovery path, rate limits, result cap, refresh cadence, and when to prefer a sibling. Nothing an agent needs before calling is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds a useful mapping from human-readable fuel names (Regular Gasoline, Additive Gasoline, Hydrous Ethanol, Diesel S10, CNG) to the Portuguese enum values an agent must actually pass. It also reinforces the 'omit cidade for statewide summary' behavior from the schema, though it adds no syntax detail for uf beyond what the schema already states.

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?

States a specific verb (queries), resource (real-time audited retail fuel prices in Brazil), the exact fuel categories covered, the data source (ANP), and the geographic scope (4,750+ stations, 27 states). An agent can immediately distinguish this from brazil_lpg_gas_prices and brazil_grocery_basket without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use brazil_list_states first to discover valid state codes (uf), or brazil_compare_regions to compare averages between two states.' Both the prerequisite step and the alternative tool for a different intent are named, so there is nothing left to inference.

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