Skip to main content
Glama

Acessos de telecom por operadora (Anatel)

acessos_telecom
Read-onlyIdempotent

Quantas linhas móveis e acessos de banda larga cada operadora tem, mês a mês (Vivo, TIM, Claro). Use quando: "quantos clientes de celular a Vivo tem?"; "participação da TIM na telefonia móvel". NÃO use para: balanço da VIVT3 ou TIMS3 → fatos_contabeis; tarifa de energia → tarifas_energia. Fonte e fórmula: dados abertos da Anatel (CC BY-ND 3.0 declarada pela Anatel, uso acertado com o órgão), somados por operadora; móvel sem M2M. Retorna: sem argumento: ranking por serviço {acessos, participacao_pct, variacao_12m_pct}; servico + cnpj (ou TOTAL): série mensal; ticker só quando o CNPJ é de empresa listada. Vazio ou erro: CNPJ sem dado devolve erro: use os 14 dígitos do ranking. O mês mais novo é preliminar. Acesso: Gratuita, sem chave.

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": "acessos_telecom"
  }
}

Input Schema

NameRequiredDescriptionDefault
deNoPrimeiro mês da série, AAAA-MM (ex.: 2024-01).
ateNoÚltimo mês da série, AAAA-MM (ex.: 2025-06).
cnpjNoCNPJ da operadora com 14 dígitos, ou TOTAL para a soma de todas. Use com `servico`.
servicoNoServiço: "movel" ou "banda_larga". Vazio = ranking dos dois; com `cnpj`, a série mensal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / servico / enum
      Added value: +[
      +  "",
      +  "movel",
      +  "banda_larga"
      +]
  2. Changed4 schema fields changed
    • addedInput schema / properties / ate / description
      Added value: +"Último mês da série, AAAA-MM (ex.: 2025-06)."
    • addedInput schema / properties / cnpj / description
      Added value: +"CNPJ da operadora com 14 dígitos, ou TOTAL para a soma de todas. Use com `servico`."
    • addedInput schema / properties / de / description
      Added value: +"Primeiro mês da série, AAAA-MM (ex.: 2024-01)."
    • addedInput schema / properties / servico / description
      Added value: +"Serviço: \"movel\" ou \"banda_larga\". Vazio = ranking dos dois; com `cnpj`, a série mensal."
  3. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, and the description adds real context beyond them: data provenance (Anatel open data, CC BY-ND), the M2M exclusion in the mobile count, the caveat that the newest month is preliminary, and free/no-key access. The error contract ('CNPJ sem dado devolve erro') is also disclosed, though the mention of a `ticker` return field that does not appear in the schema is left slightly ambiguous.

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?

Labelled blocks (Use quando / NÃO use para / Fonte e fórmula / Retorna / Vazio ou erro / Acesso) make it scannable and front-load what the tool is before routing advice. Every sentence carries information an agent would otherwise have to guess.

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?

With no output schema, the description carries the return shape itself and does so conditionally (ranking fields acessos/participacao_pct/variacao_12m_pct vs. monthly series), and it also covers the error case. For a four-parameter, all-optional read tool this is complete enough to call correctly on the first attempt.

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 coverage is 100%, so the schema already documents `de`, `ate`, `cnpj` (14 digits or TOTAL) and the `servico` enum. The description still adds usable meaning: which parameter combinations produce which output (empty = ranking of both services, `servico`+`cnpj`/TOTAL = monthly series) and a practical recipe for obtaining a valid CNPJ from the ranking when a lookup errors.

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 opening sentence gives a specific verb+resource+granularity: mobile lines and broadband accesses per operator, month by month, naming Vivo/TIM/Claro. It is impossible to confuse with siblings such as fatos_contabeis or tarifas_energia, both of which are explicitly disclaimed by name.

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?

There is an explicit 'Use quando' block with two example user questions and a 'NÃO use para' block that routes to fatos_contabeis (VIVT3/TIMS3 balance sheets) and tarifas_energia (energy tariffs). Both the positive and negative conditions are stated, plus the alternative tool to pick instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.