Skip to main content
Glama

Simulador da Reforma Tributária

calculadora_rtc_gerar_xml

Read-onlyIdempotent

Calcula a operação do regime regular (modo estrito: qualquer item inválido recusa a operação inteira) e gera o XML dos grupos de tributação IBS/CBS/IS para o documento fiscal (tipo: nfe, nfce, cte, bpe, nf3e, nfcom etc.). Mesma operacao de calculadora_rtc_regime_regular. 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_gerar_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
tipoNo
operacaoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses strict-mode semantics (any invalid item rejects the entire operation) and provenance of the calculation (official Receita Federal open-source calculators, MIT licensed, no local recalculation). It also describes part of the response via the `fonte` object, though it omits other behavioral details such as error shapes or requirements for the calculation.

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 three tight sentences with the core action front-loaded, followed by the shared-input note and provenance. It is dense but every sentence contributes; only the license mention is arguably gratuitous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool with a deeply nested required `operacao` object and no output schema, so the description should do more for the item-level fields. It compensates partially by referencing the sibling whose input schema matches and by sketching the `fonte` return value, but an agent still lacks guidance on required item structure and error behavior.

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?

Schema description coverage is 0%, so the description carries the burden. It adds real value by enumerating valid `tipo` values that the schema leaves as a bare string, and by directing readers to calculadora_rtc_regime_regular for the `operacao` contract. However, the nested `operacao`/`itens` fields (cst, cClassTrib, nbs, ncm, baseCalculo, impostoSeletivo, aliquotasNominais) remain entirely undocumented.

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 description uses specific verbs and resources: it calculates the regular-regime operation and generates the IBS/CBS/IS taxation-group XML for a fiscal document. It enumerates the document types (nfe, nfce, cte, bpe, nf3e, nfcom) and distinguishes itself from calculadora_rtc_regime_regular by noting it shares the same `operacao` input but produces XML.

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?

It gives clear context for when this tool is appropriate — when an XML of tax groups is needed for a given document type — and points to the sibling whose `operacao` contract it mirrors. It does not, however, explicitly state exclusions (e.g., when to prefer calculadora_rtc_validar_xml or the plain regime_regular calculator).

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.