Skip to main content
Glama
Sign In

Mestre Prático • Brazil Retail & Commodities MCP

by io.github.arthursantosmedia-stack
OverviewDiscussionsAdmin

brazil_lpg_gas_prices

Read-onlyIdempotent

Queries official audited retail prices of residential cooking gas (13kg LPG cylinder / Botijao de Gas GLP P13) sourced from Brazil's National Petroleum Agency (ANP) across 13,145+ authorized resellers in all 27 Brazilian states. Updated weekly with distributor markups and regional dispersion. When to use: Look up residential 13kg cooking gas prices by state or city in Brazil. When NOT to use: Do NOT use for vehicle fuels such as gasoline, ethanol, or CNG (use brazil_fuel_prices) or electricity tariffs (use brazil_energy_tariffs). Read-only and idempotent operation; no authentication required up to 60 req/min.

Input Schema

NameRequiredDescriptionDefault
ufYesTwo-letter Brazilian state code in lowercase (e.g., 'sp', 'rj', 'mg', 'ba', 'pr', 'ce', 'df'). Defaults to 'sp'.sp
cidadeNoOptional Brazilian city name or slug to filter local LPG resellers (e.g., 'sao-paulo', 'cabo-frio', 'recife'). Defaults to empty string to return statewide statistics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / uf / description
      Previous value: -"Two-letter Brazilian state code in lowercase (e.g., 'sp', 'rj', 'mg', 'ba'). Defaults to 'sp'."New value: +"Two-letter Brazilian state code in lowercase (e.g., 'sp', 'rj', 'mg', 'ba', 'pr', 'ce', 'df'). Defaults to 'sp'."
    • removedInput schema / properties / uf / enum
      Removed value: -[
-  "ac",
-  "al",
-  "am",
-  "ap",
-  "ba",
-  "ce",
-  "df",
-  "es",
-  "go",
-  "ma",
-  "mg",
-  "ms",
-  "mt",
-  "pa",
-  "pb",
-  "pe",
-  "pi",
-  "pr",
-  "rj",
-  "rn",
-  "ro",
-  "rr",
-  "rs",
-  "sc",
-  "se",
-  "sp",
-  "to"
-]
  2. Changed2 schema fields changed
    • changedInput schema / properties / uf / description
      Previous value: -"Two-letter Brazilian state code in lowercase (e.g., 'sp', 'rj', 'mg', 'ba', 'pr', 'ce', 'df'). Defaults to 'sp'."New value: +"Two-letter Brazilian state code in lowercase (e.g., 'sp', 'rj', 'mg', 'ba'). Defaults to 'sp'."
    • addedInput schema / properties / uf / enum
      Added value: +[
+  "ac",
+  "al",
+  "am",
+  "ap",
+  "ba",
+  "ce",
+  "df",
+  "es",
+  "go",
+  "ma",
+  "mg",
+  "ms",
+  "mt",
+  "pa",
+  "pb",
+  "pe",
+  "pi",
+  "pr",
+  "rj",
+  "rn",
+  "ro",
+  "rr",
+  "rs",
+  "sc",
+  "se",
+  "sp",
+  "to"
+]
  3. Changed4 schema fields changed
    • addedInput schema / properties / cidade / default
      Added value: +""
    • changedInput schema / properties / cidade / description
      Previous value: -"Optional Brazilian city name to filter local LPG resellers."New value: +"Optional Brazilian city name or slug to filter local LPG resellers (e.g., 'sao-paulo', 'cabo-frio', 'recife'). Defaults to empty string to return statewide statistics."
    • addedInput schema / properties / uf / default
      Added value: +"sp"
    • changedInput schema / properties / uf / description
      Previous value: -"Two-letter Brazilian state code (e.g., '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'). Defaults to 'sp'."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, yet the description still adds real value: rate limit ('60 req/min'), 'no authentication required', and data freshness ('updated weekly'). It does not describe the shape of the returned statistics (statewide vs city), but with annotations and a complete schema that gap is minor.

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 purpose, then cleanly segmented into when-to-use and when-not-to-use blocks; nearly every clause carries routing or scope information. Slightly padded by promotional scope numbers ('13,145+', 'all 27 states') and a vague 'regional dispersion' phrase, but no sentence is wasted overall.

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 2-parameter read-only lookup with 100% schema coverage, rich annotations, and no output schema, the description covers purpose, scope, routing, freshness, rate limits, and auth. Nothing an agent needs to invoke it correctly is missing.

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?

Schema description coverage is 100%, so both 'uf' and 'cidade' are already fully documented with defaults and examples. The description only restates the filtering dimension ('by state or city') without adding format or constraint detail, so the baseline 3 applies.

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') plus a precisely scoped resource ('official audited retail prices of residential cooking gas / 13kg LPG cylinder') with its data source (ANP) and coverage (13,145+ resellers, 27 states). It also explicitly excludes adjacent resources, so an agent can immediately distinguish it from brazil_fuel_prices and brazil_energy_tariffs.

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?

Contains explicit 'When to use' and 'When NOT to use' sections that name the correct alternative sibling for each excluded case (vehicle fuels → brazil_fuel_prices; electricity → brazil_energy_tariffs). No inference is required to route between this and its closest siblings.

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

All Mestre Prático • Brazil Retail & Commodities MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources