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

Mestre Prático & NutriPreço Official MCP Server

brazil_compare_regions

Read-onlyIdempotent

Compare weighted average prices and percentage deltas for fuels, 13kg cooking gas, and basic food basket costs between two Brazilian states. Use it to assess regional cost differences.

Instructions

Comparative synthesis tool: Compares weighted average prices and percentage deltas for fuels (gasoline, ethanol, diesel), 13kg LPG cooking gas, and basic food basket costs side-by-side between any two Brazilian states (origin UF vs. destination UF). Read-only operation; no authentication required up to 60 req/min. Use brazil_list_states to discover valid UF codes, or brazil_fuel_prices and brazil_grocery_basket for single-state station/store drilldowns.

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": {
      "origem_uf": "<origem_uf>",
      "destino_uf": "<destino_uf>"
    },
    "name": "brazil_compare_regions"
  }
}

Input Schema

NameRequiredDescriptionDefault
indicadorNoEconomic indicator category to compare (default: 'todos').
origem_ufYesOrigin two-letter Brazilian state code for comparison (e.g., 'sp', 'rj', 'ba').
destino_ufYesDestination two-letter Brazilian state code for comparison (e.g., 'mg', 'pr', 'sc').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds useful operational context: no authentication and a 60 requests/minute limit. It also indicates the comparative output nature, though it does not detail response structure or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences. It front-loads the core comparison purpose, then adds rate-limit context and sibling-tool routing without unnecessary repetition.

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?

Given rich annotations and a fully described schema, the description is largely complete for selecting and invoking the tool. A minor gap remains around how the indicador values correspond to the advertised fuels, LPG, and food-basket comparisons.

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 parameter meanings are already documented. The description adds that origem_uf and destino_uf are Brazilian state codes and points to brazil_list_states, but it does not map the indicador enum values or clarify how the food basket fits with the available enum options.

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?

The description uses a specific verb and resource: it compares weighted average prices and percentage deltas for fuels, LPG, and food baskets between two Brazilian states. It clearly distinguishes itself from sibling tools by naming drilldown alternatives for single-state analysis.

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?

It explicitly routes the agent to brazil_list_states for valid UF codes and to brazil_fuel_prices and brazil_grocery_basket for single-state drilldowns. This makes the comparison use case and alternatives clear without requiring inference.

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