Skip to main content
Glama
rtc-calculadora-mcp

rtc-calculadora-mcp

by tmoreiradev

consultar_nomenclatura

Look up NCM or NBS codes in Brazil's official nomenclature valid on a specified date, including Selective Tax status for NCM products.

Instructions

Consulta um codigo NCM (mercadoria) ou NBS (servico) na tabela oficial vigente na data. Para NCM informa tambem se o produto e tributado pelo Imposto Seletivo.

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": {
      "codigo": "<codigo>",
      "data": "<data>"
    },
    "name": "consultar_nomenclatura"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
tipoNoncm
codigoYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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, and it does disclose two useful behaviors: the lookup is versioned by date ('tabela oficial vigente na data') and NCM lookups additionally flag Imposto Seletivo taxation. It says nothing about read-only/error behavior (e.g., invalid code, code not valid at that date) or whether 'tipo' is inferred from the code.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the scope of the lookup and followed by the conditional extra output. No filler, no restatement of the tool name.

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

Completeness5/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 two required inputs are semantically covered. For a simple three-parameter read lookup this is sufficient to call correctly; the only gap, the 'tipo' enum, is a minor one.

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 must compensate, and it partially does: 'codigo' is framed as an NCM or NBS code and 'data' as selecting the table version in force. However, the 'tipo' parameter (enum ncm/nbs, default ncm) is never named, so the agent must infer its role and whether it can be omitted or overridden.

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 ('Consulta') and two concrete resources (codigo NCM for mercadoria, NBS for servico), plus a conditional output note for Imposto Seletivo. It is clear what the tool does, but it never distinguishes itself from plausible siblings such as consultar_classificacao_tributaria or consultar_aliquota_referencia.

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 only implied: you consult a code against the official table in force on a given date. There is no explicit when-to-use/when-not, no mention of prerequisites, and no routing to an alternative tool when the code is unknown or when rates rather than nomenclature are needed.

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