Skip to main content
Glama

Calculadora IBS

calculadora_rtc_validar_xml

Read-onlyIdempotent

Valida um XML contra o XSD oficial: só os grupos de tributação (subtipo 'grupo') ou a nota completa ('nota'). Devolve valido e, se inválido, a linha/coluna do erro. 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": {
      "xml": "<xml>"
    },
    "name": "calculadora_rtc_validar_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYes
tipoNo
subtipoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses the returned fields (`valido`, error line/column) and the `fonte` provenance block {repo, versao, commit, versao_base_dados}, plus the notable claim that the calculation is the official Receita Federal code with no reimplementation by the server.

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?

Four short sentences, front-loaded with the action and its scope, then the return shape, then provenance. Every sentence carries information; only the licensing/pedigree sentence is arguably incidental, though it supports trust in results.

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?

With no output schema, the description correctly takes on the job of describing return values (`valido`, error location, `fonte`), which it does completely. The remaining gap is the undocumented `tipo` parameter and the absence of any note on size limits or failure modes for malformed XML.

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 compensation is required. The description does explain the `subtipo` enum values ('grupo' = taxation groups, 'nota' = full nota), which maps directly to one parameter and constrains what `xml` should contain. But the `tipo` parameter is never mentioned and no format/syntax guidance is given for the `xml` string, leaving part of the gap unfilled.

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?

The description opens with a specific verb and resource ('Valida um XML contra o XSD oficial') and narrows the acceptable scope to taxation groups ('grupo') or the full nota ('nota'). It distinguishes the tool well from the generation/calculation siblings by making clear it only performs validation, though it never names an alternative tool explicitly.

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 through the scope constraint ('só os grupos de tributação ... ou a nota completa'), which effectively tells the agent what input forms are accepted. However, there is no explicit when-to-use statement, no when-not guidance, and no pointer to siblings such as calculadora_rtc_explicar_erro for interpreting a failed validation.

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.