Skip to main content
Glama
closermethod

EMEA Compliance MCP

get_full_emea_pack

Retrieve the complete EMEA pack with country briefs, templates, compliance requirements, stakeholder maps, and EOR handlers to equip your AI agent with full EMEA sales and employment compliance capability.

Instructions

Get the complete EMEA pack — all country briefs, all templates, all compliance requirements, stakeholder maps, and EOR handlers. Use to fine-tune your AI agent or load as system context for full EMEA capability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/main.ts:949-959 (registration)
    Tool registration in ListToolsRequestSchema handler. Defines 'get_full_emea_pack' with no required parameters — returns the complete EMEA data pack.
        {
          name: "get_full_emea_pack",
          description: "Get the complete EMEA pack — all country briefs, all templates, all compliance requirements, stakeholder maps, and EOR handlers. Use to fine-tune your AI agent or load as system context for full EMEA capability.",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        }
      ]
    };
  • Input schema for get_full_emea_pack — empty object with no required properties, since this tool returns the entire pack with no filtering.
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    }
  • Handler implementation in CallToolRequestSchema switch statement. Returns a JSON object containing all six data modules: country briefs, outreach templates, follow-up cadences, compliance checks, stakeholder maps, and EOR objection handlers.
    case "get_full_emea_pack": {
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            pack: "EMEA Compliance MCP — Complete Pack v1.0",
            author: "Elisabeth Hitz",
            credentials: [
              "5+ years EMEA enterprise sales",
              "Deel ($12B), Autodesk, Criteo, Red Points",
              "Closed deals across UK, Ireland, Spain, Germany, France, Netherlands"
            ],
            modules: {
              country_briefs: COUNTRY_BRIEFS,
              outreach_templates: OUTREACH_TEMPLATES,
              followup_cadences: FOLLOWUP_CADENCES,
              compliance_checks: COMPLIANCE_CHECKS,
              stakeholder_map: STAKEHOLDER_MAP,
              eor_objection_handlers: EOR_OBJECTION_HANDLERS
            }
          }, null, 2)
        }]
      };
    }
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, rate limits, or that it is a read-only operation. The burden is on the description but it is minimal.

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 two sentences, front-loads the purpose, and includes a clear usage suggestion with no wasted words.

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 tool with no parameters and no output schema, the description adequately explains what the pack contains. However, it lacks details on output format or size, leaving some gaps.

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

Parameters4/5

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

The tool has no parameters, so the baseline is 4. The description does not need to add parameter information, and it correctly omits it.

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 retrieves a comprehensive EMEA pack with specified components, distinguishing it from sibling tools that retrieve individual items.

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?

The description suggests using it for fine-tuning AI agents or loading as system context, which implies broad usage. However, it doesn't explicitly contrast with siblings or state when not to use.

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