Skip to main content
Glama
Sign In

Receita Federal do Brasil (Anotaê Dados Abertos)

by br.app.anotae.dados
OverviewDiscussionsAdmin

analyze_market_competition

Executa uma análise de mercado avançada sobre um segmento específico.
Retorna estatísticas consolidadas: densidade da concorrência, capital social médio, tempo de mercado e os bairros com mais concorrentes.
Suporta focar por Cidade ou por Sub-região inteira do IBGE (ex: 'Ponta Grossa', 'Curitiba').

Args:
    query: Termo de busca que define o segmento/nicho de mercado (ex: 'energia solar', 'construtora', 'pet shop').
    uf: (Opcional) Estado para concentrar a análise (ex: 'PR', 'RJ' ou 'SP').
    municipio: (Opcional) Nome da cidade para focar a análise (ex: 'Curitiba', 'Rio de Janeiro', 'São Paulo').
    regiao: (Opcional) Sub-região geográfica do IBGE para analisar todo o polo regional (ex: 'Ponta Grossa', 'Curitiba').

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": {
      "query": "<query>"
    },
    "name": "analyze_market_competition"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNo
queryYes
regiaoNo
municipioNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add real behavioral context: the four consolidated statistics returned and the fact that a 'regiao' covers an entire IBGE regional pole rather than a single city. It omits whether the call consumes credits (a credits-purchase sibling exists), whether results are cached/limited, and any cost or latency implications for an 'advanced' aggregate query.

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: purpose, then return values, then scoping capability, then the Args block. The Args block partially duplicates schema titles, but the added examples justify it and nothing is padded.

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?

An output schema exists, so the return-value sentence is redundant but harmless; the core gaps are the interaction rules among the three optional geographic filters and the credit/cost model. For a 4-parameter aggregate-analysis tool this is nearly complete.

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 0%, so the description must compensate — and it does, documenting all four parameters with the search-term semantics for 'query' and concrete examples for 'uf', 'municipio' and 'regiao'. The gap is that it never states mutual exclusivity or precedence when uf, municipio and regiao are combined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource ('Executa uma análise de mercado avançada sobre um segmento específico') and even enumerates the returned metrics (densidade da concorrência, capital social médio, tempo de mercado, bairros). It is clearly distinguishable from siblings like get_biggest_companies_by_capital or listar_subregioes_ibge, though it never says so explicitly.

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 scoping narrative ('Suporta focar por Cidade ou por Sub-região inteira do IBGE'), which tells an agent how to narrow the analysis. However, there is no explicit when-to-use/when-not guidance, no mention of complementary siblings (e.g. listar_subregioes_ibge to resolve a region name, comprar_pacote_creditos_pix for credits), and no prerequisites.

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

All Receita Federal do Brasil (Anotaê Dados Abertos) 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