Skip to main content
Glama

Mestre Prático • Brazil Retail & Commodities MCP

by io.github.arthursantosmedia-stack
OverviewDiscussionsAdmin

brazil_energy_tariffs

Read-onlyIdempotent

Provides official ANEEL residential electricity tariffs (B1) across all 27 Brazilian states (UFs) and computes thermal cooking parity comparing 13kg LPG gas cylinder vs 99 kWh induction power. When to use: Use specifically to look up residential electric kWh rates, monthly electric bills, or thermal energy parity between gas and electric cooking. When NOT to use: Do NOT use for total household cost of living (use brazil_cost_of_living) or vehicle fuel prices (use brazil_fuel_prices). Read-only and idempotent operation; zero authentication required.

Input Schema

NameRequiredDescriptionDefault
ufYesTwo-letter Brazilian state acronym (e.g., 'rj', 'sp', 'mg', 'ba', 'df'). Defaults to 'rj'.rj
consumo_kwhNoMonthly electricity consumption in kWh for residential bill calculation. Defaults to standard baseline 150 kWh.
calcular_paridade_termicaNoWhether to calculate thermal cooking parity comparing 13kg LPG cylinder vs 99 kWh induction cooking. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / consumo_kwh / minimum
      Removed value: -0
    • 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
    • addedInput schema / properties / consumo_kwh / minimum
      Added value: +0
    • 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. Changed7 schema fields changed
    • addedInput schema / properties / calcular_paridade_termica
      Added value: +{
+  "default": true,
+  "description": "Whether to calculate thermal cooking parity comparing 13kg LPG cylinder vs 99 kWh induction cooking. Defaults to true.",
+  "type": "boolean"
+}
    • addedInput schema / properties / consumo_kwh
      Added value: +{
+  "default": 150,
+  "description": "Monthly electricity consumption in kWh for residential bill calculation. Defaults to standard baseline 150 kWh.",
+  "type": "number"
+}
    • removedInput schema / properties / consumo_mensal_kwh
      Removed value: -{
-  "description": "Monthly electricity consumption in kWh for residential bill calculation. Defaults to standard baseline 150 kWh if omitted.",
-  "type": "number"
-}
    • removedInput schema / properties / incluir_paridade_termica_gas
      Removed value: -{
-  "description": "Whether to calculate thermal cooking parity comparing 13kg LPG cylinder vs 99 kWh induction cooking. Defaults to true.",
-  "type": "boolean"
-}
    • addedInput schema / properties / uf / default
      Added value: +"rj"
    • changedInput schema / properties / uf / description
      Previous value: -"Two-letter Brazilian state acronym (e.g. 'RJ', 'SP', 'MG', 'BA', 'DF'). Defaults to 'RJ' if omitted."New value: +"Two-letter Brazilian state acronym (e.g., 'rj', 'sp', 'mg', 'ba', 'df'). Defaults to 'rj'."
    • addedInput schema / required
      Added value: +[
+  "uf"
+]
  4. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the description's 'Read-only and idempotent' sentence is largely repetition and earns little credit. The one genuinely additive piece is 'zero authentication required', which annotations do not cover, plus the implicit ANEEL source authority. No discussion of output shape or what the parity computation assumes, which matters since there is no output schema.

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?

The opening sentence is front-loaded with the core purpose, followed by clearly labelled use and non-use clauses. The trailing 'Read-only and idempotent operation' clause duplicates annotation data and is the one sentence that does not fully earn its place.

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?

With three simple params, full schema coverage and no output schema, the description covers what the tool does and when to reach for it. It stops short of stating what the returned bill/parity figures include (e.g. whether ANEEL tariffs embed taxes or surcharges), which is a meaningful gap for a numeric-lookup tool with 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?

Schema coverage is 100%, so the schema already documents uf, consumo_kwh and calcular_paridade_termica including defaults, giving a baseline of 3. The description adds only the fixed constants used in parity (13kg cylinder, 99 kWh induction), which is useful but does not clarify parameter behavior beyond the schema.

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 specific verbs and resources: looks up official ANEEL residential B1 tariffs across all 27 UFs and computes thermal cooking parity (13kg LPG vs 99 kWh induction). The scope and the two distinct outputs are unambiguous, and it is clearly separable from siblings like brazil_lpg_gas_prices or brazil_cost_of_living.

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?

Provides an explicit 'When to use' list (kWh rates, monthly bills, gas-vs-electric parity) and an explicit 'When NOT to use' list routing to brazil_cost_of_living and brazil_fuel_prices by name. This is the strongest form of routing guidance: both inclusion and exclusion conditions are stated.

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