Skip to main content
Glama
rtc-calculadora-mcp

rtc-calculadora-mcp

by tmoreiradev

consultar_classificacao_tributaria

Look up an official Brazilian tax classification by 6-digit cClassTrib and date to retrieve its description, CBS/IBS reduction treatment, required NCM/NBS nomenclature, and permitted fiscal documents.

Instructions

Le na tabela oficial uma classificacao tributaria (cClassTrib, 6 digitos) vigente na data: descricao, tratamento (ex.: "Aliquota reduzida em 60%"), percentuais de reducao de CBS/IBS, nomenclatura exigida (NCM ou NBS) e documentos fiscais em que pode ser usada.

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": "consultar_classificacao_tributaria"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
tributoNocbs-ibs
c_class_tribYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 convey that this is a read of an official table and that results are versioned by date, which is genuine behavioral context. However, it says nothing about failure behavior for an unknown or expired cClassTrib, no auth/permission requirements, and it restates the return payload even though an output schema already exists.

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?

A single front-loaded sentence with a colon-delimited list of outputs; nothing is padded. The verb and resource come first, so the agent can decide quickly. Minor cost: the return-value list duplicates the output schema.

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 an output schema present, the description needn't re-explain returns, and it covers the core lookup plus date validity. Gaps remain for a 3-parameter tool with zero schema coverage: the tributo selector is unexplained and error behavior on invalid codes is unstated.

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% across 3 parameters, so the description must compensate. It adds real meaning for c_class_trib (must be 6 digits) and implies the date semantics of 'data' via 'vigente na data'. The 'tributo' parameter (enum cbs-ibs/is, default cbs-ibs) is never mentioned despite changing which reduction percentages are returned.

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?

Opens with a specific verb and resource ("Le na tabela oficial uma classificacao tributaria") and pins down the key identifying detail (cClassTrib, 6 digits) plus the validity condition. It enumerates the returned fields, so an agent knows exactly what it gets. It stops short of differentiating itself from siblings like consultar_nomenclatura or listar_situacoes_tributarias, even though it overlaps with them on nomenclature.

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

Usage Guidelines2/5

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

The description states what the tool does but never says when to choose it over an alternative, nor any exclusions or prerequisites. The phrase "vigente na data" implies a date-scoped lookup, but an agent must infer that it should call consultar_nomenclatura separately if it only needs the NCM/NBS.

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