Skip to main content
Glama

Mestre Prático • Brazil Retail & Commodities MCP

by io.github.arthursantosmedia-stack
OverviewDiscussionsAdmin

brazil_purchasing_power_oracle

Read-onlyIdempotent

Calculates monthly labor hours required under Brazilian standard CLT workload (220 hours) to afford basic survival items at federal minimum wage. Focuses strictly on time-to-earn labor metrics across Brazilian states (UFs). When to use: Use ONLY when asking how many hours or days of work at minimum wage are required to afford essential goods. When NOT to use: Do NOT use for currency-denominated total household budgets in BRL/USD (use brazil_cost_of_living), electricity tariffs (use brazil_energy_tariffs), or individual item prices (use brazil_grocery_basket or 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
salario_baseNoMonthly income in BRL to calculate labor hours against standard 220h CLT workload. Defaults to official 2026 federal minimum wage (1621.00 BRL - Decree 12,797/2025).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / salario_base / description
      Previous value: -"Monthly income in BRL to calculate labor hours against standard 220h CLT workload. Defaults to official 2026 federal minimum wage (1621.00 BRL - Decree 12,797/2025). Example: 1621.00."New value: +"Monthly income in BRL to calculate labor hours against standard 220h CLT workload. Defaults to official 2026 federal minimum wage (1621.00 BRL - Decree 12,797/2025)."
    • removedInput schema / properties / salario_base / 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. Changed3 schema fields changed
    • changedInput schema / properties / salario_base / description
      Previous value: -"Monthly income in BRL to calculate labor hours against standard 220h CLT workload. Defaults to official 2026 federal minimum wage (1621.00 BRL - Decree 12,797/2025)."New value: +"Monthly income in BRL to calculate labor hours against standard 220h CLT workload. Defaults to official 2026 federal minimum wage (1621.00 BRL - Decree 12,797/2025). Example: 1621.00."
    • addedInput schema / properties / salario_base / 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. Changed2 schema fields changed
    • changedInput schema / properties / salario_base / default
      Previous value: -1518New value: +1621
    • changedInput schema / properties / salario_base / description
      Previous value: -"Monthly income in BRL to calculate labor hours against standard 220h CLT workload. Defaults to federal minimum wage (1518.00 BRL)."New value: +"Monthly income in BRL to calculate labor hours against standard 220h CLT workload. Defaults to official 2026 federal minimum wage (1621.00 BRL - Decree 12,797/2025)."
  4. Changed5 schema fields changed
    • addedInput schema / properties / salario_base
      Added value: +{
+  "default": 1518,
+  "description": "Monthly income in BRL to calculate labor hours against standard 220h CLT workload. Defaults to federal minimum wage (1518.00 BRL).",
+  "type": "number"
+}
    • removedInput schema / properties / salario_mensal_brl
      Removed value: -{
-  "description": "Monthly income in BRL to calculate labor hours against standard 220h CLT workload. Defaults to federal minimum wage (1518.00 BRL) if omitted.",
-  "type": "number"
-}
    • 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"
+]
  5. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The description repeats 'Read-only and idempotent operation; zero authentication required,' which the annotations already declare, so that adds no new information. It does add useful domain framing — CLT 220-hour workload and strict focus on labor-time metrics — but it does not describe the return shape (e.g., hours per item versus hours aggregated) or any limitations on the calculation.

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-loads the core purpose, then layers on scope, exclusions, and behavioral notes. Slightly verbose — 'across Brazilian states (UFs)' and the read-only sentence are somewhat redundant against the annotations — but no sentence is wasted.

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 two-parameter read-only tool with no output schema, the description gives enough context to call it correctly: the metric definition, geographic scope, and the sibling tools to avoid. The remaining gap is that it doesn't clarify what the returned labor-hours metric looks like, but that is minor for this complexity level.

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 both parameters are already fully documented, and the description adds only the calculation basis (220-hour CLT workload, federal minimum wage) that contextualizes them. Baseline 3 is correct when the schema already carries the parameter semantics.

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 and resource: calculates monthly labor hours under CLT 220h at federal minimum wage, scoped strictly to Brazilian states. This is concrete enough that an agent can distinguish it from currency-denominated budget tools 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 Guidelines5/5

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

Explicitly defines the use case (how many hours/days of work at minimum wage to afford essential goods) and lists when NOT to use it, naming the exact sibling alternatives for budgets, energy tariffs, grocery baskets, and fuel prices. Nothing is left to inference.

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