Skip to main content
Glama

Employer Compensation Load

bpj_employee_cost_load
Read-onlyIdempotent

Add payroll on-costs assessed on base pay and fixed benefits to calculate annual employment cost and its loading factor.

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": {
      "salary": "<salary>",
      "payrollTax": "<payrollTax>",
      "benefits": "<benefits>"
    },
    "name": "bpj_employee_cost_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
salaryYes
benefitsYes
payrollTaxYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds computational context — that on-costs are assessed on base pay and fixed benefits, and that a loading factor is produced — but it leaves the tax base ambiguous (the description implies benefits are also assessed while the schema title says 'on base pay'), and says nothing about output format or rounding.

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?

One sentence, verb-first, with the calculation and its two outputs front-loaded and no filler or repetition of the title.

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 simple three-parameter calculator with no output schema, the description names both return values (annual cost and loading factor), which is the main thing an agent needs. It falls short only in not specifying the exact computation, particularly the treatment of benefits in the on-cost base.

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 description coverage is 0%, so the description must carry the meaning, and it only partially does: it names the conceptual inputs (base pay, fixed benefits, on-cost) and confirms the on-cost is a percentage. It does not resolve whether payrollTax applies to benefits as well as salary, which is the single most consequential ambiguity for a caller.

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 gives a specific computational verb ('Add payroll on-costs') and names both outputs ('annual employment cost and its loading factor'), so the purpose is unambiguous. It does not distinguish this from adjacent cost tools such as bpj_meeting_labor_cost or bpj_absence_cover_cost, which is why it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no statement of preconditions, and no pointer to alternative cost tools despite a large sibling catalog. The agent must infer applicability entirely from the tool name and the phrase 'annual employment cost'.

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.