Skip to main content
Glama
closermethod

EMEA Compliance MCP

get_stakeholder_map

Retrieve a stakeholder navigation map for a buyer organization based on company stage to identify decision makers, influencers, blockers, deal size, and build champion scripts before starting any deal.

Instructions

Get the multi-stakeholder navigation map for a buyer org by company stage. Shows decision maker, influencer, common blockers, average cycle, deal size range, and champion-building script. Use before starting any deal to know who you really need to convince.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_stageYes

Implementation Reference

  • Tool registration/schema definition for get_stakeholder_map - defines input validation requiring company_stage enum
    {
      name: "get_stakeholder_map",
      description: "Get the multi-stakeholder navigation map for a buyer org by company stage. Shows decision maker, influencer, common blockers, average cycle, deal size range, and champion-building script. Use before starting any deal to know who you really need to convince.",
      inputSchema: {
        type: "object",
        properties: {
          company_stage: {
            type: "string",
            enum: ["early_startup", "growth_stage", "mid_market", "enterprise"]
          }
        },
        required: ["company_stage"]
      }
    },
  • src/main.ts:921-934 (registration)
    Tool registered in ListToolsRequestSchema handler under the name 'get_stakeholder_map'
    {
      name: "get_stakeholder_map",
      description: "Get the multi-stakeholder navigation map for a buyer org by company stage. Shows decision maker, influencer, common blockers, average cycle, deal size range, and champion-building script. Use before starting any deal to know who you really need to convince.",
      inputSchema: {
        type: "object",
        properties: {
          company_stage: {
            type: "string",
            enum: ["early_startup", "growth_stage", "mid_market", "enterprise"]
          }
        },
        required: ["company_stage"]
      }
    },
  • Handler for get_stakeholder_map tool - extracts company_stage from args, looks up the STAKEHOLDER_MAP data, and returns the map as JSON
    case "get_stakeholder_map": {
      const stage = args?.company_stage as string;
      const map = STAKEHOLDER_MAP[stage as keyof typeof STAKEHOLDER_MAP];
      if (!map) throw new Error(`Unknown company stage: ${stage}`);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            module: "Multi-Stakeholder Navigation Map",
            company_stage: stage,
            ...map
          }, null, 2)
        }]
      };
    }
  • Data source (STAKEHOLDER_MAP) used by get_stakeholder_map handler - contains multi-stakeholder navigation data for early_startup, growth_stage, mid_market, and enterprise company stages
    const STAKEHOLDER_MAP = {
      early_startup: {
        company_size: "1-50 employees",
        decision_maker: "Founder / CEO — go direct, fast cycle",
        influencer: "COO or Head of Marketing/Growth",
        blockers: "Cofounder disagreement, runway anxiety, founder bandwidth",
        approach: "Short, direct, ROI-focused. Respect their time. They're firefighting daily.",
        average_cycle: "1-3 weeks",
        deal_size_range: "$3K-25K",
        champion_building_script: `"I know early-stage founders are slammed. What's the one thing that, if you saw it work in the next 30 days, would make this worth your time?"`
      },
      growth_stage: {
        company_size: "50-200 employees",
        decision_maker: "VP/Head of [function] + Founder sign-off",
        influencer: "Team lead in relevant department",
        blockers: "Internal alignment, budget cycle, prioritization",
        approach: "Connect with team lead first. Get internal champion. Then go up the chain together.",
        average_cycle: "4-8 weeks",
        deal_size_range: "$15K-100K",
        champion_building_script: `"I know this kind of decision usually involves more than one person — who else is typically involved when you're evaluating something like this? I want to make sure I'm making it easy for you to bring this to the right people."`
      },
      mid_market: {
        company_size: "200-1000 employees",
        decision_maker: "Director or VP level + Procurement",
        influencer: "Department head + Legal (for contracts)",
        blockers: "Procurement process, legal review, security review (especially for EU companies with GDPR concerns)",
        approach: "Multi-thread — connect with multiple stakeholders simultaneously. Don't rely on one champion. Map the org.",
        average_cycle: "8-16 weeks",
        deal_size_range: "$50K-500K",
        champion_building_script: `"For a deal this size, I want to make sure we're talking to all the right people from the start. Beyond yourself — who from procurement, legal, or any other team typically gets involved?"`
      },
      enterprise: {
        company_size: "1000+ employees",
        decision_maker: "C-suite sign-off, multiple VP approvals",
        influencer: "Project lead + Legal + Procurement + sometimes IT + Data Protection Officer (in EU)",
        blockers: "Procurement, legal, security review, DPO sign-off (EU), works council in Germany, integration with existing tooling",
        approach: "Map the org BEFORE outreach. Find internal champion at Director level. Build the business case for them to take upstairs. Multi-month process.",
        average_cycle: "3-9 months",
        deal_size_range: "$100K-1M+",
        champion_building_script: `"Most enterprise decisions like this involve 5-10 stakeholders. Can I share what's typically involved at companies your size, so we can plan the path together? I want to make this easy to push through internally."`
      }
    };
Behavior3/5

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

Without annotations, the description implies a read operation by saying 'Shows' and lists returned items. No mention of side effects, permissions, or data freshness, but acceptable for a simple retrieval tool.

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 short, front-loaded sentences with no waste. Efficiently communicates purpose and usage.

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?

For a simple 1-parameter tool with no output schema, the description covers purpose, returned content, and usage timing. Slightly missing details on output structure but adequate given low complexity.

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 coverage is 0% and the description only mentions 'by company stage' without explaining the enum values. The schema defines the enum but description adds minimal extra meaning beyond the parameter name.

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?

The description clearly states it retrieves a multi-stakeholder navigation map for a buyer org by company stage, listing specific content. Different from sibling tools which cover compliance, country info, etc.

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

Usage Guidelines4/5

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

Explicitly recommends using 'before starting any deal', providing clear context. Does not describe when not to use or alternatives, but the recommendation is strong.

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

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