Skip to main content
Glama
AgileConecta

mcp-fiscal-brasil

by AgileConecta
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

calcular_tributos_importacao

Estimate import tax burden for an NCM-classified product, including II, IPI, PIS/COFINS, ICMS, AFRMM, and Siscomex fees, to plan customs clearance costs.

Instructions

Calcula os tributos de importação em cascata para um produto classificado por NCM. Purpose: estimar a carga tributária de importação (II, IPI, PIS/COFINS-importação, ICMS grossed-up, AFRMM e taxa Siscomex) para planejamento de custo de desembaraço. Quando usar: ao planejar uma importação e precisar estimar o custo total de tributos. IMPORTANTE: A alíquota II (aliquota_ii) deve ser informada pelo usuário conforme a TEC vigente em www.mdic.gov.br. Não há fonte offline estruturada para a TEC. Cascata: VA -> II -> IPI (base=VA+II) -> PIS/COFINS-imp (base=VA) -> ICMS por dentro (base=VA+II+IPI+PIS+COFINS) -> AFRMM/Siscomex. DISCLAIMER: Estimativa para planejamento. Não substitui SISCOMEX nem despachante. Antidumping, regimes especiais, acordos bilaterais e alíquotas diferenciadas de PIS/COFINS estão fora do escopo do MVP. Parâmetros: ncm (8 dígitos), valor_aduaneiro (R$), uf_importador (sigla UF), aliquota_ii (% TEC), modal (maritimo/aereo/terrestre/postal), frete_maritimo (R$, apenas modal marítimo), aliquota_pis (default 2,1%), aliquota_cofins (default 9,65%), aliquota_ipi_override (sobrescreve banco NCM).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ncmYesCodigo NCM com 8 digitos (ex.: "22030000" ou "2203.00.00").
modalNoModal de transporte: "maritimo", "aereo", "terrestre" ou "postal". Afeta o AFRMM (apenas maritimo). Padrao: "maritimo".maritimo
aliquota_iiYesAliquota do II (TEC) em percentual (ex.: 20.0). Informar conforme a Tarifa Aduaneira do Brasil (www.mdic.gov.br).
aliquota_pisNoAliquota do PIS-Importacao em % (padrao: 2,1%).
uf_importadorYesSigla da UF do importador para calculo do ICMS (ex.: "SP").
frete_maritimoNoValor do frete maritimo em R$ para calculo do AFRMM. Relevante apenas quando modal="maritimo". Padrao: 0.0.
aliquota_cofinsNoAliquota do COFINS-Importacao em % (padrao: 9,65%).
valor_aduaneiroYesValor Aduaneiro (VA) em R$. Deve ser positivo.
aliquota_ipi_overrideNoSe informado, sobrescreve a aliquota IPI do banco NCM.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.5.1

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses the calculation cascade, default rates, dependency of frete_maritimo on modal, the need for user-provided II aliquota, and the non-binding disclaimer. This makes the tool's behavior transparent.

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

Conciseness3/5

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

The description is detailed but redundant: it repeats the purpose and restates the parameter list already present in the schema. It is organized with labeled sections, but the length and duplication could be trimmed without losing clarity.

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

Completeness5/5

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

Given the complexity (9 parameters, cascade calculation, defaults, and exclusions), the description provides complete context: the calculation order, default rates, modal interactions, user responsibilities, and scope limitations. Since an output schema exists, return values need not be described.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters, but the description adds significant meaning: explains the cascade order, identifies default values, clarifies modal-dependent parameters, describes the IPI override behavior, and gives NCM format examples. This goes well beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear statement of the tool's function: 'Calcula os tributos de importação em cascata para um produto classificado por NCM.' The purpose is explicit and specific, and the description distinguishes it from related tools by outlining the scope and exclusions.

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

Usage Guidelines5/5

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

Provides an explicit 'Quando usar' section and clarifies when the tool is appropriate (estimating import taxes for planning). Disclaimers about out-of-scope scenarios (antidumping, special regimes, etc.) further guide correct usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AgileConecta/RTC-MCP_FISCAL'

If you have feedback or need assistance with the MCP directory API, please join our Discord server