Skip to main content
Glama
Sign In

Observatório BR

by br.com.observatoriobr
OverviewDiscussionsAdmin

Radar de Oportunidades

get_opportunity_radar
Read-onlyIdempotent

Devolve a lista ranqueada de municípios de um critério do Radar de Oportunidades, no Brasil ou numa UF: polos (quociente locacional de uma atividade), potencial (dinamismo recente de emprego, empresas e PIB), concentracao (índice de Herfindahl-Hirschman do emprego formal) ou baixa-oferta (unidades da atividade por habitante abaixo da mediana de municípios parecidos). Cada item traz o escore e os componentes; a resposta traz o método, as fontes com período e a natureza Estimado.

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": {
      "criterion": "<criterion>"
    },
    "name": "get_opportunity_radar"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNoSigla da UF para restringir a lista (ex. "SC"). Opcional; padrão é o Brasil.
limitNoQuantos municípios devolver, de 1 a 100. Opcional; padrão 20.
sectorNoSeção da CNAE (letra de A a U, ex. "C" para indústria de transformação). Obrigatória em polos e baixa-oferta.
criterionYesCritério: "polos", "potencial", "concentracao" ou "baixa-oferta".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuine behavioral context beyond them: each item carries a score plus its components, and the response includes the method, sources with period, and the 'Estimado' nature — an important caveat that the values are estimates.

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 action and scope, then the criterion definitions in one dense sentence and the return contents in a short second sentence. Every clause carries information, though the parenthetical criterion glosses make the first sentence long.

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 no output schema, the description correctly takes on return semantics — score, components, method, sources with period, and Estimado labeling. Annotations cover safety. Minor gaps remain around pagination/limit behavior and the sector requirement for polos/baixa-oferta, but the schema handles both.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description goes further by explaining what each criterion actually measures (locational quotient, recent employment/firm/GDP dynamism, HHI of formal employment, activity units per capita below a comparable-municipality median), which meaningfully helps the agent pick a criterion beyond the bare enum list.

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: returns a ranked list of municipalities for one Radar de Oportunidades criterion, in Brazil or a single UF. It then defines all four criteria (polos, potencial, concentracao, baixa-oferta), so an agent knows exactly what is produced. No sibling tool covers this ranked-municipality view, and the definition makes that scope unambiguous.

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?

The criterion definitions imply when each mode is appropriate, and the description indicates this is a multi-municipality ranking rather than a single-territory lookup. However, it names no alternative (e.g. get_territory_profile for one municipality) and no explicit when-not-to-use condition. The sector prerequisite is only carried by the schema, not reinforced here.

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

All Observatório BR 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