Skip to main content
Glama

Ver ou ajustar os dados fiscais do emitente

emitente_fiscal

Sem argumentos, mostra o que falta para emitir nota de produto (inscrição estadual, regime tributário, séries). Com argumentos, grava: ie (inscrição estadual), crt (1 Simples Nacional, 2 Simples com excesso de sublimite, 3 regime normal, 4 MEI), fantasia, telefone e o próximo número de cada série. O CSC da NFC-e é segredo e se cadastra pela API ou pelo painel, não por aqui.

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

Input Schema

NameRequiredDescriptionDefault
ieNo
crtNo
csc_idNo
seriesNo
fantasiaNo
telefoneNo
csc_homologacao_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds valuable non-obvious behavior: the tool silently becomes a read when called with no arguments, and CSC secrets must be registered elsewhere. However, it does not say what happens to existing series/values on write (merge vs. replace) or whether re-saving is safe, which matters given idempotentHint=false.

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 the read/write dichotomy, then the field list, then the CSC caveat — a logical order with almost no filler. The crt enumeration is verbose but earns its place because the schema has no descriptions.

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 7-parameter mutation tool with zero schema coverage and no output schema, the description covers the main fields and the inspection mode. Gaps remain around the series object semantics, the CSC parameters present in the schema, and whether omitted fields are preserved or cleared on save.

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% over 7 parameters, so the description carries the burden and does explain ie, crt (including the full 1–4 regime meaning) and 'o próximo número de cada série'. But the nested series object's modelo/ambiente fields are never explained, and the description explicitly says CSC is not handled here while the schema still exposes csc_id and csc_homologacao_id — an agent cannot tell whether to pass them.

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?

The description states a specific resource (the issuer's fiscal data) and a clear dual behavior: 'Sem argumentos, mostra o que falta... Com argumentos, grava'. It does not name a sibling to contrast with (e.g. listar_configuracoes), but the verb+resource pair is unambiguous enough that an agent knows what the tool is for.

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?

The condition selecting each mode is explicit and operational: call with no arguments to inspect what is missing to issue a product invoice, call with arguments to persist values. It also excludes a related task ('O CSC... não por aqui'), which is real usage guidance. Missing are prerequisites (who may write) and any contrast with configuration-listing siblings.

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