Skip to main content
Glama
closermethod

SMB Sales Intelligence MCP

get_emea_intelligence

Get market intelligence for selling into a specific European country. Select from UK, Ireland, Spain, Germany, France, Netherlands, or Nordics.

Instructions

Get market intelligence for selling to a specific European country.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesThe EMEA market to get intelligence for

Implementation Reference

  • Tool schema registration for 'get_emea_intelligence' - defines the input schema with a 'country' enum parameter (uk, ireland, spain, germany, france, netherlands, nordics).
    {
      name: "get_emea_intelligence",
      description: "Get market intelligence for selling to a specific European country.",
      inputSchema: {
        type: "object",
        properties: {
          country: {
            type: "string",
            enum: ["uk", "ireland", "spain", "germany", "france", "netherlands", "nordics"],
            description: "The EMEA market to get intelligence for"
          }
        },
        required: ["country"]
      }
  • Handler case for 'get_emea_intelligence' - extracts the country argument and looks up data from the EMEA_INTELLIGENCE object, returning market intelligence for the specified EMEA country.
    case "get_emea_intelligence": {
      const country = args?.country as string;
      const intel = EMEA_INTELLIGENCE[country as keyof typeof EMEA_INTELLIGENCE];
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            module: "EMEA Market Intelligence",
            warning: "EMEA is not one market. Each country has different buying psychology.",
            ...intel
          }, null, 2)
        }]
      };
    }
  • src/main.ts:647-657 (registration)
    Server setup where tools are registered via ListToolsRequestSchema handler. The 'get_emea_intelligence' tool is listed among other tools in the tools array.
    const server = new Server(
      {
        name: "smb-sales-intelligence",
        version: "2.0.0",
      },
      {
        capabilities: {
          tools: {},
        },
      }
    );
  • EMEA_INTELLIGENCE data object - contains market intelligence for all 7 EMEA countries (uk, ireland, spain, germany, france, netherlands, nordics) with buyer psychology, communication styles, what works, what kills deals, email templates, sales cycles, and culture notes.
    const EMEA_INTELLIGENCE = {
      uk: {
        market: "United Kingdom",
        buyer_psychology: "Analytical and skeptical. Respond to data and specificity, not enthusiasm.",
        communication_style: "Direct but polite. Get to the point. Respect their time.",
        what_works: [
          "Concrete ROI with numbers",
          "Case studies from recognized brands",
          "Clear, specific value propositions",
          "Respecting their time — keep meetings to 30 min",
          "British spelling in all materials"
        ],
        what_kills_deals: [
          "Overselling or superlatives ('best', 'amazing', 'incredible')",
          "Aggressive follow-up — feels desperate",
          "Vague pitches without specifics",
          "American spelling (color vs colour)",
          "Showing up late or going over time"
        ],
        email_template: "Hi [Name], I came across [Company] while researching [industry] — specifically noticed [specific observation]. I help similar companies achieve [outcome]. Worth a brief call to see if there's a fit? Happy to keep it to 20 minutes.",
        sales_cycle: "2-4 weeks SMB, 6-12 weeks enterprise",
        culture_note: "Brits appreciate dry humor and self-deprecation. Don't be too earnest."
      },
      ireland: {
        market: "Ireland",
        buyer_psychology: "Relationship-first. Dublin is an EMEA tech hub, but buying culture is warmer than UK.",
        communication_style: "Warm and personal. Take time to build rapport.",
        what_works: [
          "Warmth and genuine personality",
          "Shared connections (always mention mutual contacts)",
          "Local references — show you know the Irish tech ecosystem",
          "Moving at their pace, not yours",
          "Meeting for coffee/pints when possible"
        ],
        what_kills_deals: [
          "Cold corporate tone",
          "Treating Dublin like a smaller London",
          "Rushing to close",
          "Not asking about them personally",
          "Aggressive American-style selling"
        ],
        email_template: "Hi [Name], I came across you through [connection/event]. I work with companies in the Irish tech scene on [outcome] — would love to connect if it makes sense. No pressure either way.",
        sales_cycle: "Faster with warm intros. Referrals can cut cycles in half.",
        culture_note: "The Irish tech community is tight-knit. Reputation travels fast — good and bad."
      },
      spain: {
        market: "Spain",
        buyer_psychology: "Relationship-driven and hierarchical. Trust must be established before business.",
        communication_style: "Warm but respectful of hierarchy. Decisions often require senior sign-off.",
        what_works: [
          "Building trust over multiple touchpoints",
          "Spanish language for local SMBs (English OK for international cos)",
          "Video calls or in-person — text alone is impersonal",
          "Patience — rushing is seen as disrespectful",
          "Understanding the decision-making hierarchy"
        ],
        what_kills_deals: [
          "Rushing the timeline",
          "English-only approach to local companies",
          "Going around your contact to reach their boss",
          "Following up too aggressively",
          "Scheduling during siesta (2-5pm) or Friday afternoon"
        ],
        email_template: "Hola [Name], I've been following [Company]'s growth and thought there might be a fit. I help international companies with [outcome]. Would a quick call make sense?",
        sales_cycle: "4-8 weeks SMB, 3-6 months enterprise. August is completely dead.",
        culture_note: "Barcelona-based companies tend to be more international; Madrid more traditional."
      },
      germany: {
        market: "Germany",
        buyer_psychology: "Most process-oriented market in EMEA. Analytical, risk-averse, detail-focused.",
        communication_style: "Formal, especially at first. Use Herr/Frau Last Name until invited otherwise.",
        what_works: [
          "Detailed proposals and documentation",
          "Data, case studies, and proof points",
          "Clear GDPR compliance statements",
          "Formal address (Herr/Frau) in initial contact",
          "Patience — they will analyze everything"
        ],
        what_kills_deals: [
          "Casual tone too early",
          "Vague or incomplete proposals",
          "Any hint of data privacy risk",
          "Trying to rush the process",
          "Overselling or making claims you can't prove"
        ],
        email_template: "Sehr geehrte(r) Herr/Frau [Last Name], I am reaching out regarding [specific topic]. I work with companies in [industry] on [outcome]. I would welcome the opportunity to schedule a brief call. Please find attached [relevant document/case study].",
        sales_cycle: "Longest in EMEA. 6-12 weeks SMB, 3-9 months enterprise.",
        culture_note: "Germans respect preparation. Come to meetings over-prepared, not under."
      },
      france: {
        market: "France",
        buyer_psychology: "Analytical rigor plus relationship values. Appreciate intellectual engagement.",
        communication_style: "Formal initially, warmer over time. Appreciate elegance and logic.",
        what_works: [
          "French language where possible (especially for local cos)",
          "Intellectual credibility — they respect expertise",
          "Respecting hierarchy and formal channels",
          "Quality over quantity in all communications",
          "Taking time for small talk before business"
        ],
        what_kills_deals: [
          "English-only to local French companies",
          "Generic, mass-produced messaging",
          "Aggressive follow-up — seen as crude",
          "Underestimating their sophistication",
          "Skipping the relationship-building phase"
        ],
        email_template: "Bonjour [Name], I've been following [Company] and was interested in [specific observation]. I help similar companies with [outcome]. Would a brief call make sense?",
        sales_cycle: "4-8 weeks SMB, 3-6 months enterprise. August is completely dead.",
        culture_note: "Paris vs. other French cities can have different cultures. Tech hubs exist in Lyon, Bordeaux, and Nice."
      },
      netherlands: {
        market: "Netherlands",
        buyer_psychology: "Direct, pragmatic, and egalitarian. Don't waste their time with fluff.",
        communication_style: "Very direct — they'll tell you exactly what they think.",
        what_works: [
          "Get to the point quickly",
          "Honesty and transparency (they'll call out BS)",
          "Practical value propositions",
          "Treating everyone as equals — hierarchy is flat",
          "English is widely spoken, but Dutch appreciated"
        ],
        what_kills_deals: [
          "Overpromising or exaggerating",
          "Too much small talk before business",
          "Being evasive about price or terms",
          "Hierarchy-based selling (ignoring junior team members)",
          "Fancy presentations over substance"
        ],
        email_template: "Hi [Name], I'll get straight to the point: I help companies like [similar company] with [outcome]. Is this relevant for you right now? If not, no worries.",
        sales_cycle: "Among the fastest in EMEA. 2-4 weeks SMB, 4-8 weeks enterprise.",
        culture_note: "The Dutch appreciate honesty even when uncomfortable. Don't sugarcoat."
      },
      nordics: {
        market: "Nordics (Sweden, Norway, Denmark, Finland)",
        buyer_psychology: "Consensus-driven, egalitarian, sustainability-conscious.",
        communication_style: "Reserved but friendly. Avoid hard sells.",
        what_works: [
          "Consensus-building (involve the whole team)",
          "Sustainability and ethics messaging",
          "Understated, factual communication",
          "Respecting work-life balance (no late emails)",
          "Long-term relationship focus"
        ],
        what_kills_deals: [
          "Aggressive sales tactics",
          "Ignoring junior team members",
          "Flashy or exaggerated claims",
          "Contacting outside business hours",
          "Trying to rush decisions"
        ],
        email_template: "Hi [Name], I work with companies on [outcome]. Based on what I know about [Company], there might be a fit. Would you be open to a brief conversation?",
        sales_cycle: "3-6 weeks SMB, 2-4 months enterprise. Summers (June-August) are slow.",
        culture_note: "Swedes and Finns are more reserved; Danes and Norwegians slightly warmer. All value modesty."
      }
    };
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only says 'get market intelligence,' without disclosing whether the operation is read-only, data freshness, format, or any constraints. This is insufficient for an agent to understand behavioral implications.

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 a single short sentence that conveys the essential purpose without any extraneous words. It is front-loaded and efficient.

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

Completeness2/5

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

Despite the tool's simplicity (one parameter, no output schema), the description lacks details about the nature of the intelligence, expected output format, or usage context. It feels incomplete for an agent to fully understand what the tool returns.

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

Parameters3/5

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

The schema covers 100% of parameters with a description for 'country'. The description adds the context 'for selling,' which slightly enriches understanding but does not significantly expand beyond the schema. Baseline of 3 is appropriate.

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 the action 'get' and the resource 'market intelligence for selling to a specific European country'. It is specific with a verb and resource, and distinguishes from sibling tools which cover different sales content like buying signals or call scripts.

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?

The description implies the tool is for obtaining market intelligence for European countries, but does not explicitly state when to use it vs. alternatives. There are no exclusions or references to sibling tools, leaving the decision to the agent's inference.

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/smb-sales-intelligence-mcp'

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