Skip to main content
Glama
Sign In
mcp-frete-tributario

mcp-frete-tributario

by prbretas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

calcular_carga_tributaria_frete

Calculate freight tax burden during Brazil's tax reform transition (2026-2033). Compare old ICMS/PIS/COFINS with new IBS/CBS regimes for any route and year.

Instructions

Calcula a carga tributária de um frete para um ano da transição tributária (2026–2033), comparando novo regime (IBS/CBS) com antigo regime (ICMS/PIS/COFINS).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "valorFrete": "<valorFrete>",
      "ufOrigem": "<ufOrigem>",
      "ufDestino": "<ufDestino>",
      "ano": "<ano>"
    },
    "name": "calcular_carga_tributaria_frete"
  }
}

Input Schema

NameRequiredDescriptionDefault
anoYes
ncmNo
ufOrigemYes
ufDestinoYes
valorFreteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It states the calculation and comparison but does not disclose behavioral details such as idempotency, data persistence, authentication requirements, or rate limits. The description is not contradictory but lacks depth.

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?

A single sentence that is direct and front-loaded with the core action. No redundant words. Every part contributes to the purpose.

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

Completeness2/5

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

Given 5 parameters, no output schema, and no annotations, the description is too brief. It does not specify the return format (e.g., numeric value, comparison table), nor does it explain how input parameters like UF or NCM affect the calculation. The tool's complexity demands more context.

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

Parameters2/5

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

Schema description coverage is 0%, yet the description only mentions 'ano' and the regime comparison. It does not explain 'valorFrete', 'ufOrigem', 'ufDestino', or the optional 'ncm' parameter. The description adds minimal semantic value beyond the parameter names.

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 the tax burden of freight, specifying the year range (2026–2033) and the comparison between new and old tax regimes. It distinguishes from sibling tools by focusing on freight tax calculation, not schedules, company lists, or route simulations.

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?

The description implies use for freight tax calculation but does not explicitly mention when to use this tool versus the siblings or provide exclusion criteria. No guidance on prerequisites or alternatives.

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

Deploy Server

Other Tools