Skip to main content
Glama
Sign In
radar-cnpj-mcp

radar-cnpj-mcp

by wendersoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Tendência do setor

tendencia_setor
Read-only

Compare company openings and closures by year or month to assess whether a sector or region is growing, including last 12 full months versus the previous 12. Returns aggregate totals only.

Instructions

Mostra aberturas e baixas por ano ou mês, a partir das datas da base atual, e compara os últimos 12 meses completos aos 12 anteriores. Use para saber se um setor ou região está crescendo. Período marcado como parcial não é comparável aos demais. Retorna só totais, sem listar empresas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tendencia_setor"
  }
}

Input Schema

NameRequiredDescriptionDefault
meiNoComo tratar Microempreendedores Individuais (MEI).incluir
ufsNoSiglas das UFs, ex.: ["SP", "MG"].
cnaesNoCódigos CNAE. Com 7 dígitos busca a subclasse exata; com menos dígitos busca por prefixo (ex.: "4520" = toda a classe). Use buscar_cnae para descobrir os códigos.
periodosNoQuantos períodos mostrar. Padrão: 10 anos ou 24 meses.
municipiosNoNomes dos municípios, sem diferenciar maiúsculas e acentos. Combine com ufs para evitar homônimos.
periodicidadeNoano
incluir_cnae_secundarioNoTambém considerar empresas que têm o CNAE como atividade secundária.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world, so the bar is lower, and the description still adds real behavioral context: the comparison window, that data derives from the current base's dates, that a partial period is not comparable to others, and that output is aggregates only. The only gap is the actual shape of the returned series.

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?

Four short sentences, zero filler, with the core capability front-loaded followed by the use case and two constraints. Nothing repeats the title or the schema.

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 7-parameter, no-required-argument aggregation tool with no output schema, the description covers purpose, comparison logic and a key caveat. It stops short of describing the returned structure (a series? growth percentages?), which would be the last piece an agent needs for interpreting results.

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 86%, so parameters are already well documented individually (CNAE prefix behavior, município matching, MEI handling). The description contributes the ano/mês granularity and the partial-period caveat that affects how 'periodos' should be read, but it adds no syntax or default details beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Mostra aberturas e baixas por ano ou mês') plus the comparison being made (last 12 complete months vs. previous 12). It also implicitly separates itself from the lookup siblings by noting 'Retorna só totais, sem listar empresas', though it never names the closer alternatives such as comparar_regioes or perfil_municipio.

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

Usage Guidelines4/5

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

Gives a clear when-to-use rule: 'Use para saber se um setor ou região está crescendo.' There are no explicit exclusions or named alternatives, but the use case is unambiguous enough that an agent can route here for growth questions.

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

Deploy Server

Other Tools