Skip to main content
Glama

calculadora_rtc_consultar_tabela

Read-onlyIdempotent

Consulta as tabelas oficiais da calculadora numa data de vigência. tipo: cst (CST de CBS/IBS com suas classificações), cclasstrib (classificação tributária: descrição, reduções, documentos, fundamentação), fundamentacao (fundamentações legais), ncm, nbs, atividade_simples (atividades do Simples Nacional, cAtivSN). Aceita codigos (lista, até 50) para buscar vários de uma vez, ou busca (texto) para filtrar listas (até 100 itens por resposta). Cálculo oficial das calculadoras da Reforma Tributária da Receita Federal do Brasil (código aberto, licença MIT), sem recálculo nosso. A resposta traz fonte {repo, versao, commit, versao_base_dados}.

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": {
      "tipo": "<tipo>"
    },
    "name": "calculadora_rtc_consultar_tabela"
  }
}

Input Schema

NameRequiredDescriptionDefault
anoNo
dataNo
tipoYes
buscaNo
codigosNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses that results come from the official Receita Federal open-source calculator with no recalculation by the server, and that responses carry a `fonte` block (repo, versao, commit, versao_base_dados). It also notes a response cap of roughly 100 items, which is meaningful behavioral context an agent would otherwise miss. It does not discuss errors or empty-result handling.

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?

Dense but front-loaded: the core action and the `tipo` enumeration come first, followed by the query-mode options and the provenance note. Parenthetical glosses are informative rather than padding; there is little waste, though the sentence is long and could be split for scannability.

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 read-only lookup tool with no output schema, it covers source provenance, the return envelope (`fonte`) and batching limits. Completeness is undercut only by the unexplained `ano`/`data` parameters, which matter because the whole tool is scoped to a validity date.

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?

With schema description coverage at 0%, the description must carry the load: it does an excellent job on `tipo` (glosses all six enum values), `codigos` (list, up to 50) and `busca` (text filter, ~100 items per response). But it never explains the `ano` parameter, and the `data` of vigência is only implied in the opening phrase rather than tied to the parameter — two of five parameters stay ambiguous.

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 ("Consulta as tabelas oficiais da calculadora numa data de vigência") and then enumerates each of the six `tipo` values with a short gloss (cst, cclasstrib, fundamentacao, ncm, nbs, atividade_simples). This lets an agent distinguish a reference-table lookup from calculation-oriented siblings such as calculadora_rtc_aliquotas or calculadora_rtc_base_calculo without opening the schema.

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?

It explains the two retrieval modes clearly — `codigos` to fetch several entries at once, or `busca` to filter lists — and states the batch limit of 50 codes. However, it never says when to prefer this tool over a sibling (e.g., aliquotas or base_calculo) nor any exclusion or prerequisite, so selection guidance remains implicit.

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.