Skip to main content
Glama

nfse_local_operacao

Identifies the NFS-e place of operation where IBS is due based on a six-digit Operation Indicator and transaction date.

Instructions

NFS-e: indica o local da operação (onde o IBS é devido) a partir do Indicador de Operação.

Args: c_ind_op: Código do Indicador de Operação (6 dígitos). data: Data do fato gerador (yyyy-MM-dd). Padrão: hoje.

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_ind_op": "<c_ind_op>"
    },
    "name": "nfse_local_operacao"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
c_ind_opYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state whether this is a read-only lookup, whether it hits an external service, what permissions are needed, or what happens with an invalid indicator code; only the date default is disclosed.

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 short, front-loaded sentences plus an Args block with no filler. The purpose is stated before the parameter details, which is the right order.

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?

For a small two-parameter lookup the description is nearly adequate, but with no output schema it never explains what the returned 'local' looks like (municipality code, UF, or a full address), which an agent needs in order to use the result.

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 coverage is 0%, so the description must supply meaning, and it does document both parameters: c_ind_op as a 6-digit Operation Indicator code and data as the taxable-event date in yyyy-MM-dd with today as default. It stops short of saying where the indicator code originates or what its valid ranges are.

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 specific action and outcome: it returns the place of operation (where IBS is due) derived from an Operation Indicator. The resource and the derivation source are concrete, though it does not explicitly differentiate itself from sibling lookup tools such as consultar_nbs.

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?

No guidance on when to use this versus alternatives, and no indication of where a valid c_ind_op comes from or what to do if only a municipality is known. The only implied usage is 'you have a 6-digit indicator code, get the location'.

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