Skip to main content
Glama
rtc-calculadora-mcp

rtc-calculadora-mcp

by tmoreiradev

verificar_enquadramento

Checks whether an NCM or NBS code can be used with a cClassTrib on a given date to prevent tax calculation failures like REG-011.

Instructions

Diz se um NCM ou NBS pode ser usado com a classificacao tributaria (cClassTrib) na data. Um par invalido faz o calculo do item falhar com REG-011.

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>",
      "data": "<data>"
    },
    "name": "verificar_enquadramento"
  }
}

Input Schema

NameRequiredDescriptionDefault
nbsNo
ncmNo
dataYes
c_class_tribYes

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?

No annotations are supplied, so the description carries the full burden. It does add real value by naming the downstream failure mode (REG-011) that an invalid pair triggers, which tells the agent this is a cheap validation gate. However, it never states whether the tool itself returns a negative verdict or raises an error, and it says nothing about permissions, side effects, or cost.

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, no filler, and the core purpose leads before the failure-mode detail. It is tight and well front-loaded, though it could usefully spend one more clause on the ncm/nbs selection rule instead of stopping where it does.

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 needn't be explained, and the description covers what the check means. Given four parameters at 0% schema coverage and two of them optional, the missing rule about which of ncm/nbs to pass is a real completeness gap for an agent deciding how to call it.

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 has to supply the parameter meaning; it does name NCM, NBS, cClassTrib, and the date, mapping loosely onto all four parameters. It leaves important semantics unstated: that ncm and nbs are both optional (only c_class_trib and data are required), whether one of the two must be given, and the expected date or code format.

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 and resource set: it checks whether an NCM or NBS code is compatible with a given cClassTrib on a given date. That is far more specific than restating the name 'verificar_enquadramento'. It doesn't differentiate itself from sibling tools such as consultar_classificacao_tributaria or calcular_tributos, 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 sentence about an invalid pair making the item calculation fail with REG-011 suggests this is a pre-check before calling calcular_tributos or gerar_xml_grupo. There is no explicit 'use this before X' or 'do not use this to look up codes; use consultar_nomenclatura instead'. The agent has to infer the workflow position.

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