Skip to main content
Glama
Sign In

FalaZuki Finance BR

by com.falazuki
OverviewDiscussionsAdmin

calculate_import_tax

Calcula o imposto de compra internacional (Shein, AliExpress, Amazon) com a alíquota vigente: desde 12/05/2026, zero até US$ 50 no Remessa Conforme e 60% com desconto de US$ 30 acima (Portaria MF 1.342/2026); ICMS por dentro com a alíquota do estado (17% a 20%), convertido pelo dólar do dia do Banco Central. Parâmetros obrigatórios: product_usd. Opcionais: freight_usd, remessa_conforme, icms_rate. Use exatamente estes nomes, em inglês.

Input Schema

NameRequiredDescriptionDefault
icms_rateNoAlíquota do ICMS do estado de destino, em decimal. A Receita informa de 17% a 20% conforme o estado; o padrão 0.17 é o piso dessa faixa.
freight_usdNoFrete e seguro em US$ (entram na base do imposto)
product_usdYesValor do produto em US$ (o limite do regime é US$ 3.000)
remessa_conformeNoComprado em plataforma do Remessa Conforme (Shein, AliExpress, Amazon: quase todas são)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / icms_rate
      Added value: +{
+  "default": 0.17,
+  "description": "Alíquota do ICMS do estado de destino, em decimal. A Receita informa de 17% a 20% conforme o estado; o padrão 0.17 é o piso dessa faixa.",
+  "maximum": 0.25,
+  "minimum": 0,
+  "type": "number"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it delivers unusual value: the effective tariff schedule, the ICMS 'por dentro' treatment, and that conversion uses the Banco Central dollar of the day. Gaps remain around output shape and rounding, but the core behavior 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?

Front-loads the purpose and the current rate rules in one dense but well-ordered sentence, then lists parameters. The trailing 'Use exatamente estes nomes, em inglês' is a slightly awkward meta-instruction but does earn its place by preventing localization of the argument names.

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?

For a 4-parameter calculator with no annotations and no output schema, the description supplies the tax logic and the currency-conversion rule needed to trust the result. It could have added the expected return fields (tax amount, ICMS, total) since no output schema exists, which is the only real shortfall.

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?

Schema coverage is 100%, so the baseline is 3, but the description explicitly separates the required parameter (product_usd) from the optional ones by name, reinforcing the schema's contract. It adds little about units or ranges beyond what the schema already documents, keeping it short of a 5.

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?

States a specific verb ('Calcula') and resource ('imposto de compra internacional') and names the exact scope (Shein, AliExpress, Amazon). No sibling in the list covers import tax, so it is trivially distinguishable, but the scope statement alone makes the purpose unmistakable.

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

Usage Guidelines3/5

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

It embeds the applicable regime rules (Remessa Conforme, the US$ 50 threshold, Portaria MF 1.342/2026) that determine applicability, which helps an agent judge relevance. However, there is no explicit when-to-use/when-not guidance or routing to a sibling for out-of-scope cases (e.g. non-Remessa purchases).

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

All FalaZuki Finance BR toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources