Skip to main content
Glama

calculate_vat_breakdown_latam

Read-onlyIdempotent

Calculate VAT/IVA breakdown for invoice line items in Latin American countries, grouping by tax rate and computing totals per country.

Instructions

Calculates a VAT/IVA breakdown for invoice line items in a given Latin American country, grouping amounts by tax rate and computing totals. For Brazil, returns ICMS, PIS, COFINS breakdown. For Mexico, returns IVA breakdown. For Chile/Argentina/Colombia, returns IVA breakdown. Returns { country, lines_summary, tax_breakdown, subtotal, total_tax, total }. Each line item requires { description, quantity, unit_price, tax_rate }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_codeYesTwo-letter ISO country code. Example: 'BR', 'MX', 'CL'
linesYesArray of invoice line items
currencyNoCurrency code. Example: 'BRL', 'MXN', 'CLP'. Defaults to country currency.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes
currencyYes
lines_summaryYes
tax_breakdownYes
subtotalYes
total_taxYes
totalYes
Behavior4/5

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

Annotations confirm read-only and idempotent behavior. The description adds value by detailing the return fields and country-specific tax components, exceeding annotation coverage.

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 a compact paragraph that front-loads the purpose and includes key details. It is slightly dense but not overly long, earning a 4.

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?

The description fully defines the output structure and country-specific breakdowns, compensating for the absence of an output schema in the provided context. It is complete for the tool's complexity.

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 100%, so baseline is 3. The description reiterates required line item fields and provides tax rate examples, but adds minimal new meaning beyond the schema descriptions.

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 a VAT/IVA breakdown for Latin American countries, listing specific breakdowns per country and contrasting with sibling tools by detailing the output structure.

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 description implies usage for obtaining a full tax breakdown rather than a simple amount, and the output specification guides the agent. However, it lacks explicit when-to-use or when-not-to-use compared to siblings.

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/josemvelez78/mcp-latam-business'

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