Skip to main content
Glama

Calculadora da Reforma Tributária (CBS/IBS)

calculadora_rtc_aliquotas

Read-onlyIdempotent

Alíquotas de REFERÊNCIA de CBS (União), IBS estadual (UF) e IBS municipal vigentes numa data, direto da base oficial. Recebe data (AAAA-MM-DD) ou ano, e opcionalmente uf (sigla ou código IBGE) e municipio_ibge (7 dígitos). Só devolve o que a base oficial tem: quando não há alíquota cadastrada para a data (na versão atual, só 2026 está cadastrado; de 2027 em diante a calculadora exige alíquotas informadas), a resposta diz isso em sem_aliquota_na_base e observacao, sem estimar número. 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

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

Input Schema

NameRequiredDescriptionDefault
ufNo
anoNo
dataNo
municipio_ibgeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, which already state readOnly, idempotent, non-destructive, closed-world behavior, the description discloses the empty-result contract (sem_aliquota_na_base plus observacao), the no-estimation guarantee, the data coverage boundary (2026 only), and provenance fields (repo, versao, commit, versao_base_dados). This is exactly the context the annotations cannot carry.

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?

The description is dense but front-loaded: what the tool returns, then inputs, then edge-case behavior, then provenance. Every sentence carries information. It is slightly overpacked in a single block, and requiredness is stated indirectly, but there is little waste.

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?

There is no output schema, so the description must name the important return fields, and it does: sem_aliquota_na_base, observacao, and the nested fonte object. For a read-only, zero-required-parameter lookup tool, an agent has enough to decide to call it, choose inputs, and interpret the empty case.

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 document all four parameters, and it does: data in AAAA-MM-DD, ano as a numeric alternative, uf as a two-letter code or IBGE code, municipio_ibge as a 7-digit string. It also implies at least one of data or ano is needed, which matters because the schema marks nothing as required. It does not state whether both may be passed or what happens on conflict, nor what omitting uf or municipio returns.

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 resource with scope: reference rates for CBS (federal), state IBS and municipal IBS valid on a given date, taken from the official database. That is far more than a restatement of the name. It never explicitly contrasts itself with close siblings such as calculadora_rtc_consultar_tabela or calculadora_rtc_base_calculo, so the agent must infer the boundary.

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 by strong data-availability rules: only 2026 is populated, and from 2027 onward the calculator requires rates to be supplied, so this tool will return sem_aliquota_na_base. However, there is no explicit statement of when to choose this tool over sibling tools that consume rates or fetch tables, nor of prerequisites for calling it.

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.