Skip to main content
Glama

get_full_latam_pack

Retrieve a comprehensive LATAM compliance pack with country briefs, templates, etiquette guides, and legal frameworks for AI agent fine-tuning.

Instructions

Complete LATAM pack for fine-tuning or full agent context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'get_full_latam_pack' tool. Returns a complete JSON pack containing all LATAM modules (country briefs, outreach templates, etiquette guides, follow-up cadences, stakeholder maps, and compliance checks).
    case "get_full_latam_pack": { return { content: [{ type: "text", text: JSON.stringify({ pack: "LATAM Compliance MCP v1.0", author: "Elisabeth Hitz", modules: { country_briefs: COUNTRY_BRIEFS, outreach_templates: OUTREACH_TEMPLATES, etiquette_guides: ETIQUETTE_GUIDES, followup_cadences: FOLLOWUP_CADENCES, stakeholder_map: STAKEHOLDER_MAP, compliance_checks: COMPLIANCE_CHECKS } }, null, 2) }] }; }
  • src/main.ts:145-145 (registration)
    Registration of the 'get_full_latam_pack' tool in the ListToolsRequestSchema handler. It has no required input parameters and is described as a complete LATAM pack for fine-tuning or full agent context.
    { name: "get_full_latam_pack", description: "Complete LATAM pack for fine-tuning or full agent context.", inputSchema: { type: "object", properties: {}, required: [] } }
Behavior2/5

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

No annotations provided, so description must disclose behavior. Only states purpose but no side effects, permissions, or return behavior; e.g., whether it is read-only or destructive.

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?

Single sentence, efficient and to the point. Could be more detailed, but conciseness is maintained.

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

Completeness3/5

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

Low complexity with no parameters, no output schema, and no annotations. Description is adequate but vague; 'LATAM pack' could be clarified.

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?

Input schema has no parameters (100% schema coverage), so baseline is 4. Description adds no parameter info, which is acceptable as there are none.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states it retrieves a 'complete LATAM pack' for fine-tuning or full agent context, giving a verb and resource. However, 'LATAM pack' is vague and does not differentiate clearly from siblings like get_compliance_check or get_country_brief.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage for fine-tuning or full agent context, but no explicit when-to-use, when-not-to-use, or alternatives among sibling tools.

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/closermethod/latam-compliance-mcp'

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