Skip to main content
Glama

nfse_classificacoes_por_nbs

Lists the CSTs and cClassTrib tax classifications applicable to an NFS-e service from its NBS code (no dots), with an optional date for rule lookup.

Instructions

NFS-e: lista os CSTs e cClassTrib aplicáveis a um serviço (código NBS, sem pontos).

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": {
      "nbs": "<nbs>"
    },
    "name": "nfse_classificacoes_por_nbs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nbsYes
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It implies a read-only lookup, but says nothing about whether results are versioned by date, what the second parameter does, or what fields are returned. The meaning of the optional 'data' parameter is left entirely undisclosed.

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 that states domain, action, output, and the key input format constraint. Nothing is wasted, though the density means several necessary details were dropped rather than omitted for brevity.

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

Completeness2/5

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

For a two-parameter tool with no annotations, no output schema, and 0% schema coverage, the description is too thin. It never explains the 'data' parameter, whether the lookup is date-sensitive, or what shape the returned CST/cClassTrib list takes.

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. It usefully specifies the required format of 'nbs' (code without dots), which is real added value, but leaves the optional 'data' parameter completely unexplained, so half the parameters remain opaque.

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?

Names a specific verb and resource: lists the CSTs and cClassTrib applicable to a service identified by an NBS code. The domain prefix (NFS-e) and the mention of the two returned classification codes make the purpose concrete, though it does not explicitly contrast itself with siblings such as consultar_nbs or buscar_classificacao_tributaria.

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: an agent can infer it is used when it has an NBS code and needs the applicable tax classifications. There is no statement of when not to use it, no prerequisites, and no pointer to alternatives like consultar_nbs for the code itself.

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