Skip to main content
Glama

Calculadora da Reforma Tributária (CBS/IBS)

calculadora_rtc_base_calculo

Read-onlyIdempotent

Base de cálculo UNIFICADA oficial de um item de NF-e/NFC-e (documento 'nfe') ou NFS-e ('nfse'): devolve as bases do regime regular, do Imposto Seletivo e do Simples Nacional, aplicando a vigência de cada componente no ano (com avisos de campos ignorados). Exemplo nfe: {"anoFatoGerador":2027,"tipoDocumento":55,"natureza":"bem","vProd":1000,"vFrete":50,"vDesc":50,"vICMS":180}. 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": {
      "entrada": "<entrada>"
    },
    "name": "calculadora_rtc_base_calculo"
  }
}

Input Schema

NameRequiredDescriptionDefault
entradaYes
documentoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds real behavioral context on top: it applies each component's year validity, emits warnings for ignored fields, and never recalculates locally but mirrors the official Receita Federal code. The response's `fonte` metadata block is also disclosed, though error behavior is left to a sibling.

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?

Three sentences, front-loaded with the purpose before the example and the provenance note. There is minor redundancy between 'oficial de...' and 'Cálculo oficial das calculadoras... sem recálculo nosso', but nothing wasted at length.

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?

For a computation tool with a free-form nested input and no output schema, the description usefully sketches the return (three bases plus `fonte` provenance). Yet because `entrada` accepts arbitrary keys and the description documents them only via one example, an agent cannot be confident about which fields trigger which bases or what the ignored-field warnings refer to.

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% and `entrada` is a free-form object with additionalProperties, so the schema alone conveys nothing; the example supplies seven concrete key names (anoFatoGerador, tipoDocumento, natureza, vProd, vFrete, vDesc, vICMS) which is genuinely useful. It still does not enumerate or define the full accepted key set, allowed values for `natureza`, or how the top-level `documento` parameter relates to `tipoDocumento` inside the example, so the gap is only partly closed.

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 states a concrete verb and resource: it returns the unified official calculation bases for a single NF-e/NFC-e ('nfe') or NFS-e ('nfse') line item, spanning the regular regime, Imposto Seletivo and Simples Nacional. The word 'UNIFICADA' plus the enumeration of the three bases distinguishes it from the regime-specific siblings such as calculadora_rtc_regime_regular and calculadora_rtc_simples_nacional.

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?

The scope ('base de cálculo de um item') and the inline example imply when to call it, and the mention of annual vigência hints at the year parameter's role. However, it never says when to prefer this unified call over the sibling tools that compute individual regimes or aliquotas, and states no prerequisites or 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.