Skip to main content
Glama

get_country_brief

Obtain a country-specific brief covering buyer psychology, communication styles, compliance norms, and optimal outreach times for selling in Latin America.

Instructions

LATAM country brief: buyer psychology, communication style (Spanish/Portuguese), what works/kills, sales cycle, compliance, optimal outreach times.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes

Implementation Reference

  • The handler logic for get_country_brief: looks up the country key in the COUNTRY_BRIEFS dictionary and returns a JSON response with the brief data.
    case "get_country_brief": { const d = COUNTRY_BRIEFS[country]; if (!d) throw new Error(`Unknown: ${country}`); return { content: [{ type: "text", text: JSON.stringify({ module: "LATAM Country Brief", ...d }, null, 2) }] }; }
  • Input schema for get_country_brief tool: requires a 'country' string parameter, with enum values derived from the keys of COUNTRY_BRIEFS.
    { name: "get_country_brief", description: "LATAM country brief: buyer psychology, communication style (Spanish/Portuguese), what works/kills, sales cycle, compliance, optimal outreach times.", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(COUNTRY_BRIEFS) } }, required: ["country"] } },
  • src/main.ts:137-147 (registration)
    Tool registration in ListToolsRequestSchema handler, listing get_country_brief among 7 tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        { name: "get_country_brief", description: "LATAM country brief: buyer psychology, communication style (Spanish/Portuguese), what works/kills, sales cycle, compliance, optimal outreach times.", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(COUNTRY_BRIEFS) } }, required: ["country"] } },
        { name: "get_outreach_template", description: "Country-specific outreach templates in Spanish (or Portuguese for Brazil). Calibrated to local norms.", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(OUTREACH_TEMPLATES) }, channel: { type: "string", enum: ["cold_email"] } }, required: ["country", "channel"] } },
        { name: "get_followup_cadence", description: "Country-specific follow-up cadence. Mexico/Brazil: WhatsApp central. Argentina: economic context flex. Chile: faster pace.", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(FOLLOWUP_CADENCES) } }, required: ["country"] } },
        { name: "get_etiquette_guide", description: "Business etiquette: meeting protocols, gift culture, food culture, communication norms per LATAM country.", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(ETIQUETTE_GUIDES) } }, required: ["country"] } },
        { name: "get_stakeholder_map", description: "Multi-stakeholder navigation by company stage. LATAM-specific notes (family-business dynamics, multi-country procurement).", inputSchema: { type: "object", properties: { company_stage: { type: "string", enum: Object.keys(STAKEHOLDER_MAP) } }, required: ["company_stage"] } },
        { name: "get_compliance_check", description: "Country-specific compliance: LGPD (BR), LFPDPPP (MX), Habeas Data (CO), Ley 25.326 (AR), Ley 19.628 (CL), Ley 29733 (PE).", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(COMPLIANCE_CHECKS) } }, required: ["country"] } },
        { name: "get_full_latam_pack", description: "Complete LATAM pack for fine-tuning or full agent context.", inputSchema: { type: "object", properties: {}, required: [] } }
      ]
    }));
  • The COUNTRY_BRIEFS data dictionary containing country briefs for 6 LATAM countries (Mexico, Brazil, Colombia, Argentina, Chile, Peru) with buyer psychology, communication style, what works/kills, sales cycle, compliance, and optimal outreach times.
    const COUNTRY_BRIEFS: Record<string, any> = {
      mexico: {
        market: "Mexico", flag: "🇲🇽",
        buyer_psychology: "Relationship-driven, hierarchical, formality-respecting. Trust before transaction. Family-business culture in many sectors. Strong NAFTA/USMCA influence with US business styles in border regions.",
        communication_style: "Warm but respectful. Use of usted (formal you) until invited otherwise. Indirect 'no' — 'voy a revisarlo' often means no.",
        what_works: ["Spanish-language materials (always)","Building trust over multiple meetings","Local references (Mexican companies, not just US)","Patience with timeline","WhatsApp Business is HUGE for follow-ups","In-person meals matter — comidas (long lunches) build deals","Respecting religious holidays + Día de los Muertos"],
        what_kills_deals: ["English-only outreach","Calling Mexicans 'Latinos' (they're Mexicanos)","Pushing US-style sales urgency","Skipping the relationship phase","Confusing northern (US-influenced) vs central/southern Mexico"],
        sales_cycle: "3-9 months SMB, 6-15 months enterprise. December slow (posadas), Holy Week (Semana Santa) dead.",
        compliance_note: "LFPDPPP (Ley Federal de Protección de Datos Personales en Posesión de los Particulares). INAI regulator. ARCO rights (Acceso, Rectificación, Cancelación, Oposición).",
        optimal_outreach_times: "Tue-Fri, 10am-2pm or 4pm-7pm CST/CDT. Comida 2-4pm sacred.",
        seasonal_warnings: "Semana Santa (March/April), Día de Muertos (Nov 1-2), Posadas + Christmas (Dec 16-Jan 6) all dead."
      },
      brazil: {
        market: "Brazil", flag: "🇧🇷",
        buyer_psychology: "Relationship-warm, expressive, family-oriented. Brazilians value 'jeitinho' (creative problem-solving). Hierarchical but informal in person. Long meetings, lots of side conversations.",
        communication_style: "PORTUGUESE not Spanish — common mistake by foreigners. Warm and personal. Use of 'você' standard. WhatsApp central to business communication.",
        what_works: ["Portuguese-language materials (NEVER use Spanish for Brazil)","Building strong personal rapport","WhatsApp Business is essential","Showing Brazilian customer references","Patience with extensive negotiation","In-person meetings preferred","Coffee meetings (cafezinho culture)"],
        what_kills_deals: ["Spanish materials sent to Brazil","Calling Brazilians Latin Americans without acknowledging cultural distinction","Strict deadline pressure","Skipping relationship building","Ignoring soccer/Carnaval cultural moments","Not understanding the impostos (taxes) complexity"],
        sales_cycle: "3-9 months SMB, 6-18 months enterprise. Carnaval week (Feb/Mar) dead.",
        compliance_note: "LGPD (Lei Geral de Proteção de Dados Pessoais). ANPD regulator. Strong fines (up to 2% revenue, capped R$50M per infraction).",
        optimal_outreach_times: "Tue-Fri, 10am-12pm or 2pm-6pm BRT. Lunch 12-2pm.",
        seasonal_warnings: "Carnaval (Feb/March, dates vary), Holy Week, World Cup years, June festivals (festas juninas), Christmas-New Year."
      },
      colombia: {
        market: "Colombia", flag: "🇨🇴",
        buyer_psychology: "Warm, relationship-first, formal-respectful. Bogotá business culture more formal than Medellín or coastal cities. 'Costeños' (coastal) vs 'paisas' (Medellín) vs 'rolos' (Bogotá) cultural distinctions.",
        communication_style: "Spanish, formal initially. Use of 'usted'. Polite, courteous. Direct 'no' rare — read the indirect signals.",
        what_works: ["Spanish-language outreach","Bogotá-formal vs Medellín-casual awareness","Building trust over 3-4 meetings","WhatsApp follow-ups","Coffee meeting culture","Local references (Colombian companies)"],
        what_kills_deals: ["English-only","Stereotyping (the 'narco' history is offensive)","Rushing","Confusing regional cultures","Ignoring family business dynamics"],
        sales_cycle: "3-7 months SMB, 6-12 months enterprise.",
        compliance_note: "Ley 1581 / Ley 1266 — Habeas Data. SIC regulator. Treatment of personal data with explicit consent.",
        optimal_outreach_times: "Tue-Fri, 9am-12pm or 2pm-5pm COT.",
        seasonal_warnings: "Holy Week, Día de los Muertos, Christmas + New Year, December puente (long weekends)."
      },
      argentina: {
        market: "Argentina", flag: "🇦🇷",
        buyer_psychology: "Cosmopolitan, intellectual, relationship-rich. Italian-Spanish heritage = expressive communication. Strong distrust of inflation/economic instability.",
        communication_style: "Spanish (Argentinian variant — 'vos' instead of 'tú'). Direct, sometimes blunt. Long conversations. Mate culture.",
        what_works: ["Argentine-Spanish (vos) materials","Buenos Aires-centric awareness","Patience with bureaucracy and political situations","Mate-sharing as relationship tool","Accepting that pricing in dollars is preferred (peso instability)","Accepting flexibility on payment terms"],
        what_kills_deals: ["European/Spain Spanish to Argentina","Ignoring economic context","Pushing strict timelines","Not adjusting for currency volatility","Treating Argentina like Mexico"],
        sales_cycle: "3-8 months SMB, 6-12 months enterprise. Inflation creates pricing dynamics.",
        compliance_note: "Ley 25.326 — Personal Data Protection Law. AAIP regulator. Argentina recognized as adequate by EU.",
        optimal_outreach_times: "Tue-Fri, 10am-1pm or 4pm-7pm ART. Long lunches 1-3pm.",
        seasonal_warnings: "Holy Week, summer vacation Jan-Feb (key contacts on holiday)."
      },
      chile: {
        market: "Chile", flag: "🇨🇱",
        buyer_psychology: "Pragmatic, formal, business-mature. Often called 'the Switzerland of Latin America' for stability. More direct than Mexico/Brazil but with Latin warmth.",
        communication_style: "Chilean Spanish (with unique slang). More direct in business than other LATAM. Punctuality respected.",
        what_works: ["Spanish, but Chilean variant is preferred (avoid Mexican/Spanish-Spanish slang)","Direct value propositions with numbers","Punctuality (rare in LATAM, expected in Chile)","Multi-Latin reference cases","Strong contracts and clarity"],
        what_kills_deals: ["Treating Chile like Mexico","Ignoring punctuality","Vague pricing","Not having Chile-specific case studies"],
        sales_cycle: "2-6 months SMB, 4-9 months enterprise. Among fastest in LATAM.",
        compliance_note: "Ley 19.628 — Personal Data Protection. New PDP Law in implementation 2024-2025.",
        optimal_outreach_times: "Tue-Fri, 9am-12pm or 2pm-5pm CLT.",
        seasonal_warnings: "Summer (Jan-Feb) vacation period, Holy Week, Fiestas Patrias (Sep 18-19)."
      },
      peru: {
        market: "Peru", flag: "🇵🇪",
        buyer_psychology: "Relationship-first, formal at start, family business culture. Lima coastal-business vs Andean culture. Strong respect for credentials.",
        communication_style: "Spanish, formal. Lima business culture polished. Title-respecting (Doctor, Ingeniero).",
        what_works: ["Spanish-language outreach","Lima business protocols","Long-term relationship building","Title and credential respect","Local references (Peruvian or strong LATAM)","Quality over speed"],
        what_kills_deals: ["English-only","Skipping titles/formality","Rushing decisions","Treating Peru like neighbors (each LATAM is distinct)"],
        sales_cycle: "3-8 months SMB, 6-12 months enterprise.",
        compliance_note: "Ley 29733 — Personal Data Protection. ANPDP regulator.",
        optimal_outreach_times: "Tue-Fri, 9am-12pm or 2pm-5pm PET.",
        seasonal_warnings: "Holy Week, Fiestas Patrias (Jul 28-29), Christmas-New Year."
      }
    };
Behavior3/5

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

Description discloses that the tool returns a brief covering listed topics, but no annotations exist. It does not mention any behavioral aspects (e.g., read-only nature, response format, or rate limits). Adequate but lacks depth.

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?

Single sentence front-loads the key information ('LATAM country brief') and lists relevant topics efficiently. No superfluous words.

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?

Given one parameter and no output schema, the description provides a reasonable overview of content but lacks details on return structure or format. For a simple brief tool, it is minimally complete but could be improved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

The 'country' parameter is not mentioned in the description; its role is only implied by the tool name and enum values. With 0% schema description coverage, the description should explicitly state that country specifies which LATAM country's brief to retrieve. Current description is insufficient.

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?

Description clearly states the tool provides a LATAM country brief covering specific topics (buyer psychology, communication style, etc.), distinguishing it from more specialized siblings like get_compliance_check or get_etiquette_guide. The verb 'get' is implied and the resource is well-defined.

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?

No guidance on when to use this tool versus alternatives. While the topics differentiate it, there is no explicit statement about when to prefer get_country_brief over sibling tools like get_full_latam_pack or get_compliance_check.

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