Skip to main content
Glama

get_termination_rules

Retrieve country-specific termination rules: notice periods, severance, just-cause, and pitfalls to ensure EOR compliance.

Instructions

Country-specific termination rules including notice period, severance calculation, just-cause requirements, and procedural pitfalls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes

Implementation Reference

  • src/main.ts:701-704 (registration)
    Tool registration in ListToolsRequestSchema handler — defines name, description, and inputSchema for get_termination_rules.
      name: "get_termination_rules",
      description: "Country-specific termination rules including notice period, severance calculation, just-cause requirements, and procedural pitfalls.",
      inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(COUNTRY_BRIEFS) } }, required: ["country"] }
    },
  • Handler for get_termination_rules — extracts country from args, looks up COUNTRY_BRIEFS, and returns a structured JSON response with termination-related fields (legal_framework, employee_protections, filtered common_pitfalls, and complexity-based guidance).
    case "get_termination_rules": {
      const country = args?.country as string;
      const brief = COUNTRY_BRIEFS[country];
      if (!brief) throw new Error(`Unknown country: ${country}`);
      return {
        content: [{
          type: "text", text: JSON.stringify({
            module: "Termination Rules",
            country: brief.market,
            legal_framework: brief.legal_framework,
            employee_protections: brief.notable_employee_protections,
            common_pitfalls: brief.common_pitfalls.filter(p => /termination|dismissal|fire|sever|notice|protection/i.test(p)),
            general_guidance: brief.payroll_complexity === "Very High" || brief.payroll_complexity === "High"
              ? "High-complexity termination market — formal process required, severance significant, courts often pro-employee. Use EOR for hands-off compliance."
              : "Lower-complexity termination market — process is more streamlined but still respect notice periods."
          }, null, 2)
        }]
      };
    }
Behavior3/5

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

No annotations exist; the description indicates it returns country-specific rules but does not explicitly state read-only behavior, error handling, or if any side effects occur. It adds moderate behavioral context beyond the schema.

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?

Single sentence that is well-structured, front-loads key information, and contains no fluff. Every word earns its place.

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?

With a single parameter and no output schema, the description covers the main aspects of the tool. However, it could mention the return format or what the response includes, which would enhance completeness.

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?

Schema coverage is 0% (no parameter descriptions), but the description compensates by explaining the purpose related to 'country-specific' rules. It does not add new meaning about the country parameter itself, just its role.

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 provides 'country-specific termination rules' and enumerates key components (notice period, severance calculation, just-cause requirements, procedural pitfalls), making the tool's purpose explicit and distinct from sibling tools.

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 used when termination rules are needed but does not explicitly state when to use it versus alternatives (e.g., for EOR or misclassification). No exclusion or comparison provided.

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

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