Skip to main content
Glama

SalaryNet Payroll

calculate_employer_cost

Total cost of employing someone: gross salary plus employer social security, health, pension and mandatory accruals (13th month etc.) in a supported country. Returns items, total cost, cost multiplier and sources.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>",
      "gross": "<gross>"
    },
    "name": "calculate_employer_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossYesGross salary in local currency (same period as calculate_net_pay).
countryYes
optionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "us",
      -  "ph",
      -  "ng",
      -  "id",
      -  "in",
      -  "br",
      -  "ke",
      -  "vn",
      -  "mx",
      -  "za",
      -  "tr",
      -  "co",
      -  "pk",
      -  "eg",
      -  "cl",
      -  "pe",
      -  "bd",
      -  "ar",
      -  "gh",
      -  "sa",
      -  "ae",
      -  "th",
      -  "my",
      -  "ma",
      -  "pl",
      -  "pt",
      -  "ro",
      -  "es",
      -  "kz",
      -  "uz",
      -  "lk",
      -  "np",
      -  "ec",
      -  "cr",
      -  "do"
      -]New value: +[
      +  "us",
      +  "ph",
      +  "ng",
      +  "id",
      +  "in",
      +  "br",
      +  "ke",
      +  "vn",
      +  "mx",
      +  "za",
      +  "tr",
      +  "co",
      +  "pk",
      +  "eg",
      +  "cl",
      +  "pe",
      +  "bd",
      +  "ar",
      +  "gh",
      +  "sa",
      +  "ae",
      +  "th",
      +  "my",
      +  "ma",
      +  "pl",
      +  "pt",
      +  "ro",
      +  "es",
      +  "kz",
      +  "uz",
      +  "lk",
      +  "np",
      +  "ec",
      +  "cr",
      +  "do",
      +  "et",
      +  "tz",
      +  "ug",
      +  "rw",
      +  "zm",
      +  "qa",
      +  "kw",
      +  "om",
      +  "bh",
      +  "jo",
      +  "gt",
      +  "pa",
      +  "uy",
      +  "py",
      +  "bo"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "us",
      -  "ph",
      -  "ng",
      -  "id",
      -  "in",
      -  "br",
      -  "ke",
      -  "vn",
      -  "mx",
      -  "za",
      -  "tr",
      -  "co"
      -]New value: +[
      +  "us",
      +  "ph",
      +  "ng",
      +  "id",
      +  "in",
      +  "br",
      +  "ke",
      +  "vn",
      +  "mx",
      +  "za",
      +  "tr",
      +  "co",
      +  "pk",
      +  "eg",
      +  "cl",
      +  "pe",
      +  "bd",
      +  "ar",
      +  "gh",
      +  "sa",
      +  "ae",
      +  "th",
      +  "my",
      +  "ma",
      +  "pl",
      +  "pt",
      +  "ro",
      +  "es",
      +  "kz",
      +  "uz",
      +  "lk",
      +  "np",
      +  "ec",
      +  "cr",
      +  "do"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "us",
      -  "ph",
      -  "ng",
      -  "id",
      -  "in",
      -  "br",
      -  "ke",
      -  "vn"
      -]New value: +[
      +  "us",
      +  "ph",
      +  "ng",
      +  "id",
      +  "in",
      +  "br",
      +  "ke",
      +  "vn",
      +  "mx",
      +  "za",
      +  "tr",
      +  "co"
      +]
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does well on output surface—items, total cost, cost multiplier and sources are all named—and the term 'accruals (13th month etc.)' flags that non-obvious cost components are included. However, it says nothing about what happens with an unsupported country, what the free-form options object controls, or whether results are estimates tied to a tax year or jurisdiction version.

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?

Two sentences, no filler. The cost definition is front-loaded and the return summary is compacted into a single trailing clause. Nothing repeats the tool name or wastes tokens.

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

Completeness3/5

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

There is no output schema, and the description does supply a minimal return summary, which is appropriate. Still, for a tool whose country enum spans roughly fifty entries and whose options object is untyped, the definition leaves real gaps: no guidance on the options contents, currency handling, or behavior outside the supported set. It is adequate but not complete.

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 only 33%, so the description should compensate more than it does. It does clarify that 'gross' is gross salary and that country must be supported, which reinforces the existing schema text. But the third parameter, an open-ended options object with additionalProperties and no documented keys, is entirely unaddressed in both schema and description—the one place added explanation was most needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific computation (total employer cost) and enumerates the components folded into it: gross salary, employer social security, health, pension and mandatory accruals such as 13th month. That is far more informative than a restatement of the tool name. It does not explicitly contrast itself with the sibling calculate_net_pay, leaving the agent to infer the direction (employer cost vs employee net).

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 phrase 'in a supported country' hints that a country must be one from an allowed list, which loosely points toward list_countries, but no alternative is named and no condition for choosing this tool over calculate_net_pay is stated. The schema's parenthetical '(same period as calculate_net_pay)' is the only explicit relational cue and it appears in the schema, not the description. Usage is implied rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources