Skip to main content
Glama

consultar_ncm

Retrieve the hierarchical description and Imposto Seletivo status for an 8-digit NCM code to verify tax classification before calculating CBS, IBS, or Imposto Seletivo.

Instructions

Consulta uma NCM (8 dígitos, sem pontos): descrição hierárquica e se é tributada 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": {
      "ncm": "<ncm>"
    },
    "name": "consultar_ncm"
  }
}

Input Schema

NameRequiredDescriptionDefault
ncmYes
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the expected input format and the nature of the result, which implies a read-only query, but it says nothing about what happens with an invalid or unformatted code, whether the response is a hierarchy tree or a flat string, or any lookup latency/limits.

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?

A single compact sentence with the resource, its format constraint, and the returned fields, all front-loaded. Nothing is redundant and it fits its one-line purpose well.

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?

With no output schema and no annotations, the description should fully carry both behavior and return shape; it names the returned fields but not their structure or error behavior, and leaves the 'data' parameter unexplained. Adequate to attempt a call, but incomplete for a two-parameter tool.

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 does for the required 'ncm' parameter by specifying 8 digits without punctuation. The second parameter 'data' (nullable, default null) is never mentioned, leaving its meaning — presumably an effective-date or table-version selector — entirely undocumented.

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 gives a specific verb ("Consulta") and resource ("NCM") plus the two things returned: "descrição hierárquica" and whether it is taxed by the Imposto Seletivo. It does not distinguish itself from lookup siblings such as consultar_nbs or buscar_classificacao_tributaria, so it stops short of a 5.

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: the input constraint (8 digits, no dots) signals it is a code-lookup tool, but there is no explicit when-to-use guidance, no exclusions, and no pointer to the sibling to use for broader classification searches. The agent must infer the placement in the workflow.

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