Skip to main content
Glama
closermethod

EMEA Compliance MCP

get_eor_objection_handler

Resolve EOR and global hiring objections with country-specific responses for EMEA, covering contractor use, commitment, cost, entity, and compliance.

Instructions

Handle EOR (Employer of Record) and global hiring objections with country-specific responses. Built from 3+ years selling EOR at Deel and Multiplier across EMEA. Covers: 'use contractors instead', 'not ready to commit', 'too expensive', 'we have entity', 'compliance unclear'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eor_objectionYes

Implementation Reference

  • src/main.ts:935-948 (registration)
    Tool registration in ListToolsRequestSchema handler. Defines the tool name, description, and input schema with the 'eor_objection' enum.
    {
      name: "get_eor_objection_handler",
      description: "Handle EOR (Employer of Record) and global hiring objections with country-specific responses. Built from 3+ years selling EOR at Deel and Multiplier across EMEA. Covers: 'use contractors instead', 'not ready to commit', 'too expensive', 'we have entity', 'compliance unclear'.",
      inputSchema: {
        type: "object",
        properties: {
          eor_objection: {
            type: "string",
            enum: ["use_contractors_instead", "not_ready_to_commit", "too_expensive", "we_already_have_entity", "compliance_unclear"]
          }
        },
        required: ["eor_objection"]
      }
    },
  • Input schema for the get_eor_objection_handler tool. Requires eor_objection string with enum values for 5 objection types.
        type: "object",
        properties: {
          eor_objection: {
            type: "string",
            enum: ["use_contractors_instead", "not_ready_to_commit", "too_expensive", "we_already_have_entity", "compliance_unclear"]
          }
        },
        required: ["eor_objection"]
      }
    },
  • Handler case in CallToolRequestSchema. Looks up the objection key in EOR_OBJECTION_HANDLERS and returns the full handler data as JSON.
    case "get_eor_objection_handler": {
      const objection = args?.eor_objection as string;
      const handler = EOR_OBJECTION_HANDLERS[objection as keyof typeof EOR_OBJECTION_HANDLERS];
      if (!handler) throw new Error(`Unknown EOR objection: ${objection}`);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            module: "EOR / Global Hiring Objection Handler",
            ...handler
          }, null, 2)
        }]
      };
    }
  • The EOR_OBJECTION_HANDLERS data object. Contains 5 objection handlers each with objection text, psychology explanation, response script, follow-up suggestion, country risk levels, and mistakes to avoid.
    const EOR_OBJECTION_HANDLERS = {
      use_contractors_instead: {
        objection: "We'll just hire them as contractors instead of going through EOR",
        psychology: "They're optimizing for cost or simplicity but underestimating misclassification risk.",
        response: `"That's a common path — the catch is misclassification risk. In countries like Germany, Spain, and France, if a contractor is found to function as an employee (continuous engagement, exclusive work, set hours), the back-payment of social contributions and fines can be 5-10x what you saved. Plus the worker can sue for employee rights retroactively.
    
    EOR removes that risk entirely. Worth a quick look at your specific exposure?"`,
        follow_up: "Offer a 15-min misclassification risk assessment specific to their target country",
        countries_high_risk: ["germany", "france", "spain"],
        countries_lower_risk: ["uk_post_brexit", "ireland"],
        mistake_to_avoid: "Don't fearmonger — explain the actual mechanism (labor courts, social contributions, employee retroactive rights)"
      },
      not_ready_to_commit: {
        objection: "We're not ready to commit to a permanent hire in [country]",
        psychology: "They're hesitant about making a long-term commitment in an unfamiliar market.",
        response: `"That's actually exactly when EOR is most useful. EOR lets you hire someone in [country] without setting up a legal entity, AND you can terminate the arrangement with much lower risk than a direct hire — typically 30-60 day notice depending on country.
    
    It's literally designed for the 'we want to test this market' situation. What's your timeline for getting this person started?"`,
        follow_up: "Frame as 'low-commitment trial' rather than 'first step to bigger commitment'",
        mistake_to_avoid: "Don't push toward permanence; embrace the trial framing"
      },
      too_expensive: {
        objection: "EOR markup is too expensive compared to direct hire",
        psychology: "They're comparing apples to oranges — direct hire costs include entity setup.",
        response: `"Fair to ask. Quick math: setting up a legal entity in [country] typically costs $20-50K upfront (lawyers, accountants, registration), takes 3-6 months, plus ongoing monthly compliance ($1-3K/month for accounting/legal/tax filings).
    
    EOR gets you compliant in 7-14 days for typically 10-15% markup on payroll. For 1-3 hires per country, EOR is dramatically cheaper. The break-even vs entity is usually 5-10 employees.
    
    How many hires are you planning in [country] over the next 12 months?"`,
        follow_up: "Use their headcount projection to do live ROI math in the conversation",
        mistake_to_avoid: "Don't argue percentage markup — argue total cost of ownership"
      },
      we_already_have_entity: {
        objection: "We already have a legal entity in [country], we don't need EOR",
        psychology: "Valid pushback IF they have actual operational entity. Often they have a paper entity without HR/payroll capabilities.",
        response: `"That's great. Quick clarifying questions: does your entity have local payroll, statutory benefits administration, employment contract templates that comply with [country] labor law, and someone managing local HR queries from employees?
    
    If yes, EOR is unnecessary. If you're outsourcing any of that to local accountants or law firms, EOR often consolidates those costs into one bill — and reduces compliance risk."`,
        follow_up: "Use their answers to identify where EOR actually adds value despite their entity",
        mistake_to_avoid: "Don't assume their entity is fully operational"
      },
      compliance_unclear: {
        objection: "I'm not sure if EOR is even legal/proper in [country]",
        psychology: "Risk-averse buyer wants reassurance. Common in Germany, France, Switzerland.",
        response: `"Totally fair — and good instinct to ask. EOR is legally established and standard in [country]. The arrangement is: the EOR provider is the legal employer of record (handling all compliance, taxes, social contributions, statutory benefits), and your company directs the employee's work.
    
    In [country] specifically, [country-specific legal framework: e.g., Germany's Arbeitnehmerüberlassungsgesetz (AÜG) for staffing arrangements, France's portage salarial laws, etc.]
    
    I can share the specific legal framework and case law. Want me to send that over?"`,
        follow_up: "Send country-specific compliance whitepaper or send to their legal team directly",
        mistake_to_avoid: "Don't be vague about legal framework — name the actual statute"
      }
    };
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions the source of the responses but does not describe side effects, authentication requirements, rate limits, or whether the tool is read-only. This is insufficient for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with three sentences that front-load the core purpose. Each sentence adds value (purpose, credibility, coverage). No unnecessary words.

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?

With no output schema and only one simple parameter, the description still fails to explain what the tool returns or how the handler is invoked. It does not cover expected output format or behavior, leaving the agent without sufficient context to use the tool effectively.

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 input schema has one parameter with an enum of 5 values and 0% schema description coverage. The description lists similar objection labels but does not provide additional meaning about each value's context or expected usage. The parameter semantics are only marginally clarified.

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 tool handles EOR objections with country-specific responses, listing five specific objection types. This distinguishes it from sibling tools like 'get_compliance_check' or 'get_outreach_template', which address different sales support needs.

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 usage when encountering EOR objections by listing covered scenarios, but it lacks explicit when-to-use or when-not-to-use instructions, and does not mention alternative tools for related tasks.

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