Skip to main content
Glama
nikolasdehor

mcp-fiscal-brasil

by nikolasdehor
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

calcular_tributos_importacao

Calculate import tax cascade for a product using NCM, value, and state to estimate total customs clearance costs including II, IPI, PIS/COFINS-import, ICMS grossed-up, AFRMM, and Siscomex.

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

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. It transparently describes the calculation cascade step by step, warns about external data dependency, and notes scope limitations (no antidumping, regimes especiais, etc.).

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?

The description is lengthy but well-structured with sections (Purpose, When to use, Cascata, DISCLAIMER, Parâmetros). Every sentence adds value, though some redundancy could be trimmed.

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 tool's complexity (9 parameters, cascade formula, multiple taxes), the description is thorough. It explains the math, required external data, and limitations. With an output schema likely present, it is complete.

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

Parameters4/5

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

Input schema has 100% coverage with descriptions for all parameters. The description adds extra context about defaults (e.g., aliquota_pis default 2.1%) and explains the cascade, complementing the schema well.

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?

The description clearly states the tool calculates import taxes (II, IPI, PIS/COFINS, ICMS, AFRMM, Siscomex) for NCM-classified products, distinguishing it from sibling tools like consultar_aliquotas_importacao which retrieve rates rather than computing total burden.

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 says 'When to use: when planning an import and needing to estimate total tax cost.' Includes guidance on obtaining the II rate from an external source and lists exclusions. Does not explicitly contrast with siblings, but context implies this is for calculation.

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/nikolasdehor/mcp-fiscal-brasil'

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