Skip to main content
Glama

Simulador da Reforma Tributária

calculadora_rtc_regime_regular

Read-onlyIdempotent

Calcula CBS, IBS (UF e município) e Imposto Seletivo de uma operação do REGIME REGULAR (LC 214/2025) pela calculadora oficial da Receita, com erros por item (um item inválido não derruba os outros). Recebe operacao no JSON oficial. Exemplo: {"id":"op-1","versao":"1.0.0","dhFatoGerador":"2026-03-10T10:00:00-03:00","municipio":5002704,"uf":"MS","itens":[{"numero":1,"ncm":"84713012","cst":"000","cClassTrib":"000001","baseCalculo":1000,"quantidade":1,"unidade":"UN"}]}. Em 2026 as alíquotas vêm da base oficial e aliquotasNominais não é aceito; a partir de 2027 aliquotasNominais é obrigatório em cada item e o resultado sai como simulado. Retorna memoria (por item: estado, base, alíquota, redução, alíquota efetiva e valor de CBS/IBS-UF/IBS-Mun/IS, CST/cClassTrib, erros e o texto oficial de memória de cálculo com a norma), totais e resultado_oficial (JSON da Receita, intacto). Item com erro traz o código REG-xxx, descrito no catálogo oficial de calculadora_rtc_explicar_erro. 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": {
      "operacao": "<operacao>"
    },
    "name": "calculadora_rtc_regime_regular"
  }
}

Input Schema

NameRequiredDescriptionDefault
operacaoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare the safe, idempotent, closed-world profile, and the description still adds substantial operational detail: per-item error isolation (one invalid item doesn't sink the rest), the exact response sections (memoria, totais, resultado_oficial), the untouched official JSON pass-through, and a fonte block with repo/version/commit/data version. It also discloses that no recalculation is performed internally, which tells the agent results are authoritative rather than derived.

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-loads what is computed, then the example, then version rules, then return shape — a sensible order. It is dense but each block earns its place; minor redundancy between 'pela calculadora oficial da Receita' and the later 'Cálculo oficial ... sem recálculo nosso' sentence.

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 must explain returns and does: memoria per item (state, base, rate, reduction, effective rate, tax values, CST/cClassTrib, errors, official calculation-memo text) plus totais and resultado_oficial. It also covers error handling, the error-catalog sibling, and data provenance, leaving little an agent needs unknown before calling.

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 0% and the single parameter is a deeply nested object, so the description carries the burden. It supplies a full worked example showing required top-level fields and an item shape, plus the version-dependent behavior of aliquotasNominais, which the schema lists but never explains. Gaps remain for lesser fields (nbs, impostoSeletivo, quantidade semantics), so not a 5.

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 concrete verb and the exact tax set computed (CBS, IBS-UF, IBS-município, Imposto Seletivo) for a named regime (REGIME REGULAR, LC 214/2025) using the Receita's official calculator. That regime qualifier is what distinguishes it from the sibling simples_nacional calculator without needing to open either schema.

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?

Implicitly scopes usage to regime-regular operations and routes error-code lookups to calculadora_rtc_explicar_erro (REG-xxx codes). It also gives a rule-based condition for parameter choice: aliquotasNominais is rejected in 2026 and mandatory from 2027. It never says explicitly 'do not use this for Simples Nacional operations', so the exclusion is inferred from the name rather than stated.

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.