Skip to main content
Glama
rtc-calculadora-mcp

rtc-calculadora-mcp

by tmoreiradev

gerar_xml_grupo

Computes the operation in strict mode and generates the official IBSCBS/IS tax group XML, per item and totals, for a given fiscal document type. Outputs the same operation format as tax calculation.

Instructions

Calcula a operacao em modo estrito e gera o XML oficial dos grupos de tributacao (IBSCBS/IS por item e totais) para o documento tipo. Mesmo formato de operacao de calcular_tributos.

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": "gerar_xml_grupo"
  }
}

Input Schema

NameRequiredDescriptionDefault
tipoNonfe
operacaoYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose 'modo estrito' (strict evaluation, implying hard failures rather than lenient output) and that output is the official XML broken down per item plus totals. It says nothing about side effects, error behavior under strict mode, or whether the calculation is pure/deterministic.

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?

Two sentences, front-loaded with the action and the output artifact, then the cross-reference to `calcular_tributos`. No filler; the only mild weakness is that the parenthetical field list interrupts the first sentence.

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?

An output schema exists, so return values need not be explained, and the `operacao` shape is delegated to a named sibling. What remains missing is the cost of 'strict mode' — what makes an operation fail, and whether the generated XML is validated on the way out — which matters for a tool that produces an official document.

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 coverage is 0%, so the description must compensate. It does add real value by pointing to `calcular_tributos` as the reference for the `operacao` shape, but since `operacao` is an open nested object with additionalProperties=true, the agent still gets no hint of which fields are required versus optional. `tipo` is fully covered by its enum and default, so no description help is needed there.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (compute in strict mode + generate official XML) and a specific resource (IBS/CBS/IS tax groups, per item and totals) scoped by the `tipo` document. This clearly differs from `calcular_tributos`, which only computes. It stops short of 5 only because the phrase 'grupos de tributacao' is left for the reader to interpret.

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 description implies this is the XML-emitting counterpart to `calcular_tributos` and that speed/behavior is 'strict mode', but it never says when to choose it over `calcular_tributos` or `validar_xml`, nor whether validation precedes or follows. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.