Skip to main content
Glama

validar_nomenclatura_aplicavel

Validates whether an NCM or NBS code is compatible with cClassTrib on a specified date, helping prevent REG-011 errors in tax calculations.

Instructions

Valida se uma NCM (mercadoria) ou NBS (serviço) é compatível com a cClassTrib na data.

Informe ncm OU nbs. Retorna valido: true/false. Evita o erro REG-011 no cálculo.

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": {
      "c_class_trib": "<c_class_trib>"
    },
    "name": "validar_nomenclatura_aplicavel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nbsNo
ncmNo
dataNo
c_class_tribYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/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 signals a read-only validation, discloses the return shape (`valido: true/false`) that the absent output schema does not, and flags date sensitivity ('na data'). It does not say what happens if both `ncm` and `nbs` are supplied, if neither is supplied, or what `data` defaults to.

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?

Three short lines, front-loaded with the action, then the input constraint, then the return value. Every sentence carries information, though the trailing error-code note ('Evita o erro REG-011') reads as a dangling justification rather than integrated guidance.

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?

Covers purpose, input exclusivity, and return value for a tool with no output schema and no annotations, which is a reasonable amount. Gaps remain around date format/default, behavior on conflicting or missing NCM/NBS, and how an invalid result should be interpreted — relevant for a validation gate ahead of tax calculation.

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 identifies three of the four parameters by name and explains the NCM/NBS domain split (merchandise vs service) plus the date dimension, but adds no format, default, or exclusivity-error semantics for `data` or `c_class_trib`.

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 and resource (validate NCM or NBS compatibility with cClassTrib on a given date) and disambiguates from the lookup siblings consultar_ncm/consultar_nbs by framing this as a compatibility check rather than a code lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit calling constraint ('Informe `ncm` OU `nbs`') and a motivating use case (avoiding error REG-011 during calculation), which tells the agent this is a pre-flight check before tax calculation. It does not name consultar_ncm/consultar_nbs or buscar_classificacao_tributaria as alternatives or state when not to use it.

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