Skip to main content
Glama

get_stakeholder_map

Map stakeholders for LATAM sales by company stage, incorporating family-business dynamics and multi-country procurement insights.

Instructions

Multi-stakeholder navigation by company stage. LATAM-specific notes (family-business dynamics, multi-country procurement).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_stageYes

Implementation Reference

  • Data definition (schema) for the STAKEHOLDER_MAP constant. Maps 4 company stages (early_startup, growth_stage, mid_market, enterprise) to decision_maker, influencer, latam_note, cycle, and deal_size.
    const STAKEHOLDER_MAP: Record<string, any> = {
      early_startup: { decision_maker: "Founder / Director General", influencer: "Co-founder", latam_note: "Family-business dynamics frequent.", cycle: "1-4 months", deal_size: "$3K-30K" },
      growth_stage: { decision_maker: "CEO + Director", influencer: "Department head", latam_note: "Brazil: family-business approval cycles slow. Argentina: economic context affects timing.", cycle: "3-7 months", deal_size: "$10K-100K" },
      mid_market: { decision_maker: "C-suite + Procurement + Legal", influencer: "Multiple department heads", latam_note: "Mexico: comité de dirección. Brazil: familia owners.", cycle: "6-12 months", deal_size: "$50K-500K" },
      enterprise: { decision_maker: "Multi-stakeholder C-suite + family + board (in family conglomerates)", influencer: "Project lead + external consultants", latam_note: "Multi-country LATAM expansions need country-by-country approach. Brazil and Mexico often separate procurement processes from rest of LATAM.", cycle: "9-24 months", deal_size: "$200K-5M" }
    };
  • src/main.ts:137-147 (registration)
    Tool registration in ListToolsRequestSchema handler. Defines 'get_stakeholder_map' with name, description, and inputSchema requiring 'company_stage' (enum from STAKEHOLDER_MAP keys).
    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: [] } }
      ]
    }));
  • Handler implementation inside CallToolRequestSchema switch statement. Extracts company_stage from args, looks up STAKEHOLDER_MAP[stage], and returns JSON-stringified result with module name and company_stage.
    case "get_stakeholder_map": { const stage = args?.company_stage as string; const d = STAKEHOLDER_MAP[stage]; if (!d) throw new Error(`Unknown stage: ${stage}`); return { content: [{ type: "text", text: JSON.stringify({ module: "LATAM Stakeholder Map", company_stage: stage, ...d }, null, 2) }] }; }
Behavior3/5

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

No annotations exist; description mentions LATAM-specific notes (family-business dynamics, multi-country procurement) adding behavioral context, but does not disclose return value structure or side effects.

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?

Two sentences, front-loaded with action and context, no wasted words. Efficient and clear.

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

Completeness4/5

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

Given low complexity (1 param, no output schema), the description covers the core purpose and relevant LATAM context. Minor gap: no mention of output format or prerequisites, but largely adequate.

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 has one parameter with 0% description coverage; description only says 'by company stage' without explaining the enum values (early_startup, growth_stage, etc.) or how they affect the output.

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?

Clearly states the tool provides multi-stakeholder navigation with LATAM-specific context (family-business dynamics, multi-country procurement), distinguishing it from sibling tools 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 Guidelines3/5

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

Implies usage for stakeholder mapping in LATAM contexts via company stage, but lacks explicit when-to-use or when-not-to-use guidance relative to siblings.

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