Skip to main content
Glama

get_statutory_benefits

Identify required statutory benefits for a country: pension, health, vacation, holidays, parental leave, 13th salary, and bonuses. Ensure compliance with local labor laws.

Instructions

Required statutory benefits per country: pension, health, vacation, holidays, parental leave, 13th salary, bonuses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes

Implementation Reference

  • src/main.ts:705-709 (registration)
    Tool registration for get_statutory_benefits in the ListToolsRequestSchema handler
    {
      name: "get_statutory_benefits",
      description: "Required statutory benefits per country: pension, health, vacation, holidays, parental leave, 13th salary, bonuses.",
      inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(COUNTRY_BRIEFS) } }, required: ["country"] }
    },
  • Handler implementation for get_statutory_benefits: looks up country from COUNTRY_BRIEFS and returns statutory benefits data including required benefits (must_haves), employer tax burden, and employee protections.
    case "get_statutory_benefits": {
      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: "Statutory Benefits",
            country: brief.market,
            required: brief.must_haves,
            employer_tax_burden: brief.tax_burden_employer,
            employee_protections: brief.notable_employee_protections
          }, null, 2)
        }]
      };
    }
  • Input schema for get_statutory_benefits: requires a country parameter (string, must be one of the defined country keys)
      inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(COUNTRY_BRIEFS) } }, required: ["country"] }
    },
Behavior3/5

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

No annotations provided; description states what the tool returns but does not disclose read-only nature, potential rate limits, or output format. For a simple lookup, it is minimally adequate but not rich in behavioral context.

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 with no wasted words. Lists relevant benefit examples succinctly. Front-loaded with purpose and scope.

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?

Given no output schema and one simple parameter, the description is nearly complete. Could explicitly state return format (e.g., list of benefit names), but the examples hint at the output. High completeness for a low-complexity tool.

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%; however, the single parameter 'country' is an enum with clear values. The description mentions 'per country' but does not explain the parameter beyond that. Baseline 3 is appropriate given the enum clarity.

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?

Description clearly states the tool returns required statutory benefits per country, with specific examples (pension, health, etc.). It distinguishes well from siblings like get_termination_rules or get_visa_paths by focusing on benefits.

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?

Usage is implied (use when you need statutory benefits for a country), but there is no explicit guidance on when not to use, prerequisites, or alternatives. The tool is straightforward, but the description lacks contextual cues.

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