Skip to main content
Glama

indicadores_por_uf

Read-onlyIdempotent

Retrieve Brazilian state-level indicators for unemployment, income, employment, or GDP, filtered by state and sorted by current value, with prior-period and year-over-year comparisons.

Instructions

Indicador das 27 Unidades da Federação (IBGE), no último período divulgado, com comparação.

indicador: desocupacao (PNAD, trimestral), rendimento (rendimento médio real, trimestral), massa_rendimento (trimestral), ocupados (trimestral) ou pib (PIB corrente por UF, anual). uf filtra por nome, sigla ou código (ex.: 'bahia', 'BA', '29'). ordenar é 'maior' ou 'menor' pelo valor atual. periodos (1 a 12) é quantos períodos recentes buscar. A resposta traz uma tabela com: uf, codigo, valor, anterior (período anterior), ano_anterior (mesmo período do ano anterior) e variacao (em pontos percentuais para taxas, em % para os demais).

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": {
      "indicador": "<indicador>"
    },
    "name": "indicadores_por_uf"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNo
ordenarNomaior
periodosNo
indicadorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 openWorldHint, so safety is covered; the description adds genuinely new behavioral context: data freshness (last published period), source periodicity (quarterly vs annual) and, importantly, the exact response columns including variacao, with its unit differing between rates (percentage points) and other series (%). That unit distinction materially affects interpretation.

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 the one-line purpose, then parameter guidance, then response shape. Dense but every clause carries information an agent needs; only minor tightening (e.g. repeating 'trimestral' four times) would improve it.

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?

There is no output schema, and the description compensates by naming the returned columns and their meaning, including how variacao is computed and in which unit. Combined with full parameter documentation and existing annotations, an agent has everything needed to call and interpret this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and no parameter is an enum, so the description carries the full burden and does: `indicador` is enumerated with five accepted values and their periodicity, `uf` accepts name, abbreviation or numeric code with concrete examples, `ordenar` takes 'maior' or 'menor' by current value, and `periodos` is bounded to 1-12. This is far beyond what the bare schema conveys.

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 resource (indicators for the 27 Brazilian states from IBGE), the time scope (last published period) and the distinctive comparison output, and enumerates the five supported indicators with their periodicity. An agent can tell this is a sub-national, latest-period comparison tool rather than a generic series fetcher.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied through the parameter explanations (filter by UF, sort by current value, fetch N recent periods) but there is no explicit when-to-use versus alternatives such as buscar_indicadores, comparar_series or obter_serie. The multi-indicator, multi-UF comparison capability is the natural selection criterion, yet it is left for the agent to infer.

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