Skip to main content
Glama

get_outreach_template

Generate country-specific outreach templates in Spanish or Portuguese for cold email campaigns, calibrated to local norms in Latin American markets.

Instructions

Country-specific outreach templates in Spanish (or Portuguese for Brazil). Calibrated to local norms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes
channelYes

Implementation Reference

  • The handler function for the get_outreach_template tool. Looks up OUTREACH_TEMPLATES by country and channel, returns JSON with module, country, channel, and template data. Throws error if not found.
    case "get_outreach_template": { const channel = args?.channel as string; const d = OUTREACH_TEMPLATES[country]?.[channel]; if (!d) throw new Error(`No template for ${country}/${channel}`); return { content: [{ type: "text", text: JSON.stringify({ module: "LATAM Outreach Template", country, channel, ...d }, null, 2) }] }; }
  • Input schema registration for get_outreach_template. Defines required parameters: country (enum from OUTREACH_TEMPLATES keys) and channel (currently only 'cold_email').
    { 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"] } },
  • src/main.ts:140-140 (registration)
    Tool registration in ListToolsRequestSchema handler. The tool 'get_outreach_template' is registered with its description and input schema.
    { 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"] } },
  • OUTREACH_TEMPLATES data structure containing cold_email templates for 6 LATAM countries (Mexico, Brazil, Colombia, Argentina, Chile, Peru). Each template includes subject, body, and psychology notes.
    const OUTREACH_TEMPLATES: Record<string, Record<string, any>> = {
      mexico: {
        cold_email: { subject: "[Empresa] + [Resultado] — vale una llamada?", body: "Hola [Name],\n\nHe estado siguiendo a [Company] y me llamó la atención [observación específica].\n\nTrabajamos con empresas como la suya en [outcome]. Aquí hay un caso reciente: [resultado de cliente].\n\n¿Vale la pena una llamada de 15 minutos?\n\nSaludos cordiales,\n[Your name]", psychology: "Spanish opener + Mexican formal. Vale (worth) is a Mexican-friendly word." }
      },
      brazil: {
        cold_email: { subject: "Vale uma conversa rápida sobre [topic]?", body: "Olá [Name],\n\nEspero que esteja bem. Acompanhei [Company] e fiquei impressionado com [observação].\n\nTrabalhamos com empresas brasileiras em [resultado]. Recente: [client result].\n\nVale 15 minutos para conversar?\n\nUm abraço,\n[Your name]", psychology: "PORTUGUESE not Spanish. 'Um abraço' (a hug) close is warm and Brazilian." }
      },
      colombia: {
        cold_email: { subject: "[Empresa] — una pregunta rápida", body: "Buenos días [Name],\n\nLe escribo porque he estado siguiendo el crecimiento de [Company]. Trabajamos con empresas colombianas en [outcome].\n\nReferencias recientes: [Cliente X resultado].\n\n¿Estaría dispuesto/a a una llamada de 15 minutos?\n\nQue tenga buen día,\n[Your name]", psychology: "Buenos días opener. 'Que tenga buen día' is polite Colombian closing." }
      },
      argentina: {
        cold_email: { subject: "Hola [Name] — una consulta", body: "Hola [Name],\n\nVi lo que estás haciendo con [Company] y me interesó [observación]. Trabajamos con empresas argentinas en [outcome] — pricing flexible considerando el contexto local.\n\nReferencia: [cliente local].\n\n¿Te interesaría una llamada de 15 min?\n\nSaludos,\n[Your name]", psychology: "Argentine Spanish 'vos' implied. 'Pricing flexible' acknowledges peso instability." }
      },
      chile: {
        cold_email: { subject: "Consulta directa para [Company]", body: "Estimado/a [Name],\n\nLe escribo brevemente. Trabajamos con empresas chilenas en [outcome con números]. Cliente reciente: [resultado específico].\n\n¿Una llamada de 15 minutos esta semana?\n\nAtentamente,\n[Your name]", psychology: "Direct + numbers. Chileans appreciate efficiency." }
      },
      peru: {
        cold_email: { subject: "[Doctor/Ingeniero] [Last name] — propuesta breve", body: "Estimado/a [Doctor/Ingeniero] [Last name],\n\nReciba un cordial saludo. Trabajamos con empresas peruanas en [outcome] y consideramos que podría ser de valor para [Company].\n\nReferencias: [casos relevantes].\n\nQuedo atento/a a su disponibilidad.\n\nCordialmente,\n[Your name]", psychology: "Title-respecting (Doctor/Ingeniero common). Formal Peruvian Lima business style." }
      }
    };
  • src/main.ts:154-154 (registration)
    Case branch in CallToolRequestSchema switch that dispatches to the outreach template handler when name is 'get_outreach_template'.
    case "get_outreach_template": { const channel = args?.channel as string; const d = OUTREACH_TEMPLATES[country]?.[channel]; if (!d) throw new Error(`No template for ${country}/${channel}`); return { content: [{ type: "text", text: JSON.stringify({ module: "LATAM Outreach Template", country, channel, ...d }, null, 2) }] }; }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool returns (templates) but does not mention whether it is read-only, whether it triggers side effects, authentication requirements, rate limits, or error handling.

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 extremely concise with two short sentences, no redundant information. Every character adds value.

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?

For a simple retrieval tool with two enum parameters and no output schema, the description covers the core intent (country-specific templates in local language). However, it lacks details on return format, error scenarios, or how language switching works (explicitly 'Portuguese for Brazil' is noted but not automated mechanism). Adequate but could be more thorough.

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?

Schema description coverage is 0%, so the description must compensate. It adds value for the country parameter by mentioning 'Spanish (or Portuguese for Brazil)', but does not explain the 'channel' parameter or its single enum value 'cold_email'. No guidance on format or constraints beyond the schema itself.

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

Purpose4/5

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

The description clearly states the tool provides country-specific outreach templates with language details (Spanish/Portuguese). It distinguishes from siblings like 'get_etiquette_guide' and 'get_country_brief' by specifying templates rather than general guidance. However, it could be more explicit about the type of templates (e.g., email templates).

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?

The description implies usage for country-specific outreach but offers no explicit guidance on when to use this tool versus alternatives, nor when not to use it. No mention of prerequisites or exclusions.

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