Skip to main content
Glama

Mestre Prático • Brazil Retail & Commodities MCP

brazil_cost_of_living

Read-onlyIdempotent

Computes the total estimated monthly household expenditure budget in Brazilian Reais (BRL) and USD across Brazilian states. Aggregates monthly food, baseline utilities, and standard domestic maintenance into a single consolidated currency figure. When to use: Use ONLY to retrieve the estimated total monthly financial expenditure in BRL or USD to live in a given state. When NOT to use: Do NOT use for labor-hour working time metrics (use brazil_purchasing_power_oracle), individual electricity tariffs (use brazil_energy_tariffs), or raw commodity prices (use brazil_fuel_prices or brazil_grocery_basket). Read-only operation; no authentication required up to 60 req/min.

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_cost_of_living"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufYesTwo-letter Brazilian state code (e.g., 'sp', 'rj', 'df', 'mg'). Defaults to 'sp'.sp
converter_usdNoWhen true, converts all BRL cost metrics into USD using live exchange rates. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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. Changed1 schema field changed
    • 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. Changed5 schema fields changed
    • removedInput schema / properties / comparar_com_dolar
      Removed value: -{
      -  "description": "When true, converts all BRL cost metrics into USD using live exchange rates.",
      -  "type": "boolean"
      -}
    • addedInput schema / properties / converter_usd
      Added value: +{
      +  "default": false,
      +  "description": "When true, converts all BRL cost metrics into USD using live exchange rates. Defaults to false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / uf / default
      Added value: +"sp"
    • changedInput schema / properties / uf / description
      Previous value: -"Two-letter Brazilian state code (e.g., 'sp', 'rj', 'df'). Defaults to national average if omitted."New value: +"Two-letter Brazilian state code (e.g., 'sp', 'rj', 'df', 'mg'). Defaults to 'sp'."
    • addedInput schema / required
      Added value: +[
      +  "uf"
      +]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the 'Read-only operation' phrase is largely redundant. However the description adds genuinely new context beyond annotations: no authentication required and a 60 req/min rate limit, plus what the aggregate is composed of (food, baseline utilities, domestic maintenance). It stops short of explaining exchange-rate sourcing for the USD conversion or whether figures assume a fixed household size.

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?

Purpose is front-loaded and the when/when-not structure is easy to parse. There is some redundancy: 'When to use: Use ONLY to retrieve the estimated total monthly financial expenditure' restates the opening sentence, and 'Read-only operation' repeats the annotations, but no sentence is harmful.

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 tool with no output schema, the description covers purpose, exclusions, what the number aggregates, and operational limits (auth-free, 60 req/min). Remaining gaps—household-size assumptions and USD conversion mechanics—are minor but real.

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 'converter_usd' are already documented with defaults and examples. The description only adds that USD uses live exchange rates, which is already in the schema; it adds no new constraint or format detail. Baseline 3 applies when the schema does the heavy lifting.

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 ('Computes the total estimated monthly household expenditure budget in BRL and USD across Brazilian states') and even names the components aggregated. An agent can distinguish it from every sibling 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?

Explicit 'When to use' restricted scope (total monthly expenditure for a given state) plus a 'When NOT to use' list that routes four sibling tools to their correct purposes (purchasing power, energy tariffs, fuel prices, grocery basket). 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.