Skip to main content
Glama

Simulador da Reforma Tributária

calculadora_rtc_simples_nacional

Read-onlyIdempotent

Calcula CBS e IBS de uma operação de empresa do SIMPLES NACIONAL pela calculadora oficial da Receita (NT 2026.005), com erros por item. Recebe operacao no JSON oficial. Exemplo: {"id":"op-1","versao":"2.0.0","data":"2027-03-15","tpDoc":"55","CRT":"1","itens":[{"numero":1,"cAtivSN":"01","cClassTrib":"000001","baseCalculo":"950.00","valorImpostoSeletivo":"0.00","pIBSSN":"1.25","pCBSSN":"2.75"}]}. Retorna memoria (por item: receita bruta, base, alíquotas e valores de IBS/CBS do Simples, valores pendentes/suspensos, total do item, erros VSN-xxx), totais e resultado_oficial. A lista de atividades válidas (cAtivSN) está em calculadora_rtc_consultar_tabela, tipo atividade_simples. 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_simples_nacional"
  }
}

Input Schema

NameRequiredDescriptionDefault
operacaoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With annotations already flagging readOnly/idempotent/closed-world, the description adds meaningful behavior: results come from the open-source Receita calculator with no recalculated values, errors are returned per item with VSN-xxx codes, and a `fonte` block with repo/version/commit is included. It does not cover rate limits or performance, but the critical trust/provenance behavior is disclosed.

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 the purpose sentence, then the input contract, then the return shape and the table reference. Dense but every block (example, memoria/totais/resultado_oficial, fonte) serves a purpose; the license/source note is slightly verbose but relevant to trust.

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 single nested-object parameter with no output schema and no field-level schema docs, the description supplies the example payload, the return structure, error codes and the lookup tool for enum-like values. Remaining gaps are the semantics of individual fields (tpDoc, versao, cClassTrib) rather than the overall contract.

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 carry the burden; it does so with a full worked example of the `operacao` object covering id, versao, data, tpDoc, CRT and item fields, plus a pointer to the table tool for cAtivSN values. It leaves the meaning/valid values of fields like tpDoc, CRT and cClassTrib unexplained.

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 (calcula) and resource (CBS e IBS) scoped to SIMPLES NACIONAL companies, names the official basis (calculadora da Receita, NT 2026.005), and notes per-item errors. This makes it clearly distinguishable from calculadora_rtc_regime_regular and the other calculadora_* siblings.

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?

Establishes the context of use (SIMPLES NACIONAL operations, official JSON format) and cross-references calculadora_rtc_consultar_tabela for the valid cAtivSN list. It does not explicitly say when to pick this over calculadora_rtc_aliquotas or regime_regular, so no exclusions.

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.