Skip to main content
Glama

calculate_vat_amount_latam

Read-onlyIdempotent

Compute tax amounts from net or gross inputs using country-specific VAT rates and labels for Latin American markets. Supports building invoice calculators and checkout flows.

Instructions

Calculates tax amounts from either a net (excluding tax) or gross (including tax) amount for a given tax rate, with country context for currency and tax label. Returns { country, net_amount, tax_amount, gross_amount, tax_rate, tax_label, currency }. Use when building pricing tools, invoice calculators, or checkout flows across LatAm markets that need to split gross prices into net + tax components.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_codeYesTwo-letter ISO country code for currency and context. Example: 'BR', 'MX', 'CL'
amountYesThe amount to calculate tax for
tax_rateYesTax rate as a percentage. Example: 16 for 16% IVA (Mexico) or 19 for 19% IVA (Chile)
amount_typeYesWhether the input amount is net (excluding tax) or gross (including tax)
currencyNoOverride currency. Defaults to country currency.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes
net_amountYes
tax_amountYes
gross_amountYes
tax_rateYes
tax_labelYes
currencyYes
Behavior4/5

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

Discloses return object shape; idempotent and read-only nature already in annotations. Adds value with country context for currency/tax label.

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?

Two sentences, no redundancy, front-loaded with action and output, followed by appropriate use cases.

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?

Provides return format, use context, and input semantics; no edge cases or error handling mentioned, but sufficient for a calculation tool with clear schema.

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 covers all parameters with descriptions; description adds general context but no new detail beyond schema (e.g., example values or validation rules).

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 verb 'calculates' on tax amounts, specifies net/gross input and output structure. Distinguishes from sibling tools like calculate_vat_breakdown_latam by focusing on net-to-gross split with country context.

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 states use cases (pricing tools, invoice calculators, checkout flows) but does not mention when not to use or list alternatives like calculate_vat_breakdown_latam.

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