Skip to main content
Glama

Simulador da Reforma Tributária

calculadora_rtc_explicar_erro

Read-onlyIdempotent

Explica códigos de erro das calculadoras oficiais: REG-xxx (regime regular) e VSN-xxx (Simples Nacional), com título, descrição e orientação do catálogo oficial. Aceita uma lista de códigos. 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": {
      "codigos": "<codigos>"
    },
    "name": "calculadora_rtc_explicar_erro"
  }
}

Input Schema

NameRequiredDescriptionDefault
codigosYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 value beyond that: it clarifies there is no recalculation performed on our side, that results come from the official open-source MIT-licensed RFB calculator, and that the response carries provenance metadata (repo, versao, commit, versao_base_dados). It does not say what happens with unknown or malformed codes.

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-loaded with the purpose, then the input shape, then the behavioural/provenance notes — a sensible order with no filler. The licensing parenthetical and the sentence about 'sem recálculo nosso' are slightly digressive but each carries informational weight.

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?

There is no output schema, but the description compensates by enumerating what the answer contains (título, descrição, orientação, and the fonte block), which is what an agent needs to decide to call it. For a single-parameter lookup tool the coverage is close to sufficient; only edge-case behaviour is unaddressed.

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?

The single parameter has 0% schema description coverage, so the description must carry the semantics — and it does, stating that a list of codes is accepted and giving the expected code formats (REG-xxx, VSN-xxx). It still leaves open whether the list may mix both families and how invalid codes are reported, which keeps it short of 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 specific verb ("Explica") applied to a specific resource ("códigos de erro") and names the exact code families covered (REG-xxx for regime regular, VSN-xxx for Simples Nacional), plus the returned fields. An agent can immediately tell this apart from calculation siblings like base_calculo or aliquotas purely from the description.

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 rather than stated: it's clear this is the tool to call when you have an error code from the official calculators, but there is no explicit when-to-use vs. when-not, and no sibling is named as an alternative or complement. The reference to the official catalogue hints at the domain but does not route the agent between this and, say, consultar_tabela.

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.