Skip to main content
Glama

consultar_nbs

Look up an NBS service code (no dots) to get its description and taxation data for verifying tax treatment in CBS, IBS, and Imposto Seletivo calculations.

Instructions

Consulta uma NBS (código de serviço, sem pontos): descrição e dados de tributação.

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

Input Schema

NameRequiredDescriptionDefault
nbsYes
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/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 does disclose that this is a read lookup returning a description plus taxation data, which is real value, but it says nothing about what happens with an unknown code, whether the result is cached/current, or what 'sem pontos' enforcement looks like.

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 compact sentence with the key input constraint front-loaded and the returned fields appended. Nothing is padded, though the strict 'sem pontos' rule is buried in a parenthetical rather than stated as a directive.

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?

The tool is simple (2 params, no nested objects, no output schema), and the description covers the lookup and roughly what comes back. It falls short on the undocumented 'data' parameter and on any failure behavior, which an agent would need to call it reliably.

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

Parameters2/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, and it only partially does. It clarifies the 'nbs' parameter (a dotless service code), but the second parameter 'data' — plausibly a reference date for the tax figures — is never mentioned in the description or the schema.

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?

States a concrete verb ('Consulta') and resource ('NBS') and previews the payload ('descrição e dados de tributação'). The parenthetical 'código de serviço, sem pontos' distinguishes it from code lookups of other domains (e.g. consultar_ncm) and from the classification-list sibling, though no sibling is named explicitly.

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 you call this to resolve a service-code description and its tax treatment. There is no statement of when to prefer it over nfse_classificacoes_por_nbs or buscar_classificacao_tributaria, and no prerequisites or error conditions are given.

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