Skip to main content
Glama

buscar_classificacao_tributaria

Queries CBS/IBS tax classifications (cClassTrib) by code, CST, supplier, buyer, DF-e, or text, returning applicable rates, reductions, and credit details for accurate tax calculation.

Instructions

Consulta classificações tributárias (cClassTrib) de CBS/IBS.

Escolhe a consulta conforme os filtros informados:

  • c_class_trib (+ sigla_dfe opcional): detalhe completo de uma cClassTrib (tipo de alíquota, percentuais de redução, crédito, nomenclatura exigida etc.).

  • cst: todas as cClassTrib de um CST.

  • fornecedor/adquirente (ATOR_ID) e/ou sigla_dfe: cClassTrib aplicáveis aos atores/DF-e.

  • nenhum dos acima: lista geral; use busca para filtrar por texto (ex: 'medicamento', 'educação', 'alimentação humana').

Args: data: Data do fato gerador (yyyy-MM-dd). Padrão: hoje. c_class_trib: Código da cClassTrib (6 dígitos). cst: Código do CST (3 dígitos). sigla_dfe: Sigla do DF-e (ex: 'NFE', 'NFCE', 'NFSE'). fornecedor: ATOR_ID do fornecedor. adquirente: ATOR_ID do adquirente. busca: Texto para filtrar por código/descrição (listas). limite: Máximo de itens retornados em listas (padrão 50).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buscar_classificacao_tributaria"
  }
}

Input Schema

NameRequiredDescriptionDefault
cstNo
dataNo
buscaNo
limiteNo
sigla_dfeNo
adquirenteNo
fornecedorNo
c_class_tribNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/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 read-only query semantics, sensible defaults (data = hoje, limite = 50), and the shape of the detailed result (tipo de alíquota, percentuais de redução, crédito, nomenclatura exigida). It does not cover error conditions or what happens when filters conflict or return nothing, so it falls just short of fully transparent.

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?

Front-loaded with purpose, then a routing block, then a parameter block — a logical order with no filler. The Args section is long but necessary given zero schema description coverage, though it slightly duplicates the schema property titles.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter read tool with no annotations and no output schema, the definition covers routing, defaults, and return-content hints adequately. Minor gaps remain around truncation/pagination beyond `limite` and behavior on empty or ambiguous filter combinations, but an agent can call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates completely: every one of the 8 parameters gets format detail (yyyy-MM-dd, 6-digit cClassTrib, 3-digit CST, DF-e sigla examples, ATOR_ID integers, default 50 for limite) plus the conditional interaction between c_class_trib and sigla_dfe.

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 ('Consulta classificações tributárias (cClassTrib) de CBS/IBS') and immediately enumerates the distinct query modes, so an agent knows exactly which data domain this covers versus siblings like consultar_nbs or consultar_ncm.

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

Usage Guidelines5/5

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

The bullet list explicitly maps each filter combination (c_class_trib, cst, fornecedor/adquirente + sigla_dfe, none) to the resulting query, and it names the fallback ('use `busca` para filtrar por texto') for the no-filter case. This is a complete when-to-use routing table rather than implied guidance.

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