Skip to main content
Glama

Listar configurações fiscais recentes

listar_configuracoes
Read-onlyIdempotent

Últimas combinações realmente usadas de serviço, CNAE, NBS e tributação. Use configuracao_id em emitir_nota. Se houver ambiguidade, pergunte ao usuário — não escolha nem invente código fiscal.

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

Input Schema

NameRequiredDescriptionDefault
limiteNoMáximo de combinações (1–20, padrão 8).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new behavior: results are limited to combinations 'realmente usadas', meaning the list can be incomplete and is usage-derived rather than a full fiscal-code catalog — critical context. The explicit anti-hallucination warning about fiscal codes is also behavioral guidance not present in any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler, with the resource definition front-loaded and the downstream usage plus safety caveat following. Every clause earns its place and nothing is repeated from the schema or annotations.

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?

No output schema exists, so the description must carry the return picture — it does by naming the combination fields and implying a configuracao_id is returned. Minor gap: it tells the agent to use configuracao_id in emitir_nota but never explicitly confirms that configuracao_id is part of each returned item, leaving that inference to the caller.

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 100% and the single parameter 'limite' already documents its range (1–20) and default (8). The description adds nothing about the parameter, so the schema does all the work. Baseline 3 applies.

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 verb+resource: retrieves the most recent combinations of serviço, CNAE, NBS and tributação that were actually used. An agent can distinguish this from listar_notas/listar_tomadores by the resource, though it never explicitly contrasts itself with those siblings. The scope qualifier 'realmente usadas' is the key differentiator and is present.

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

Usage Guidelines4/5

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

Explicitly routes the agent forward: 'Use configuracao_id em emitir_nota' names the consuming sibling tool. It also gives a negative rule ('Se houver ambiguidade, pergunte ao usuário — não escolha nem invente código fiscal'), which is exactly the kind of when-not guidance that prevents bad emission. It stops short of stating when to prefer this list over e.g. listar_tomadores, but the context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources