Skip to main content
Glama

get_invoice_requirements_latam

Read-onlyIdempotent

Retrieve mandatory electronic invoice fields for Latin American countries. Validate invoice templates against official tax authority requirements for NF-e, CFDI, DTE, and more.

Instructions

Returns the mandatory fields required on a valid electronic invoice for a given Latin American country, based on official tax authority requirements. Returns { country, invoice_type, mandatory_fields: [], electronic_system, notes }. Covers NF-e/NF-C (Brazil), CFDI 4.0 (Mexico), DTE (Chile), Factura Electrónica (Argentina/Colombia). Use when generating invoices for LatAm customers, validating invoice templates, or building invoice compliance checks in agent workflows. Information provided as reference only — not legal advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_codeYesTwo-letter ISO country code. Example: 'BR', 'MX', 'CL', 'AR', 'CO'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNo
invoice_typeNo
mandatory_fieldsNo
electronic_systemNo
notesNo
disclaimerNo
errorNo
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds useful context: the information is based on official tax authority requirements, is for reference only, and not legal advice. No contradictions with annotations.

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?

The description is concise with four sentences, front-loaded with the primary purpose. Every sentence adds value, with no redundant information.

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 output schema exists, the description adequately covers the tool's purpose, usage context, limitations, and behavioral notes. 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.

Parameters4/5

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

Schema coverage is 100% with a description for 'country_code'. The description adds examples and the list of covered countries (BR, MX, CL, AR, CO), adding value beyond the schema.

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 returns mandatory fields for electronic invoices in specific Latin American countries, with a specific verb 'Returns' and resource 'mandatory fields'. It differentiates from sibling tools by listing covered countries and use cases.

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 provides explicit use cases: generating invoices, validating templates, and compliance checks. It also includes a disclaimer about not being legal advice. However, it does not explicitly state when not to use the tool or alternatives.

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