validalatam-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | No | If set, calls go through RapidAPI (validalatam.p.rapidapi.com). Optional API key. | |
| VALIDALATAM_BASE_URL | No | Override API base URL | https://validalatam.ia-latam.app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_documentB | Validate/normalize/format a LatAm document (AR_CUIT, BR_CPF, BR_CNPJ, MX_RFC, MX_CURP, CL_RUT, CO_NIT, PE_RUC, IBAN...). type='AUTO' auto-detects. |
| validate_batchC | Validate up to 1000 items, each {type, value, country?}. |
| generate_test_dataC | Generate clearly FAKE, check-digit-valid test values for a document type. |
| list_document_typesA | List supported document type codes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: single validation, batch validation, test data generation, and listing supported types. There is no overlap in functionality or ambiguity about when to use each tool.
All tool names follow a consistent verb_noun pattern: validate_document, validate_batch, generate_test_data, list_document_types. The pattern is predictable and easy to understand.
With only 4 tools, the set is well-scoped and each tool serves a clear, non-redundant purpose. The count is appropriate for a focused validation service.
The tools cover the full lifecycle of document validation: discovery of types, single validation with normalization/formatting, batch validation for bulk needs, and generation of test data. No obvious gaps exist for the stated purpose.