reference-data

compute_employment_cost

Read-onlyIdempotent

PAID ($0.05). Cost to employ: prices every statutory contribution on both the employee and employer sides for a gross salary, returning line-by-line amounts with instrument citations and an explicit refused list for schemes that could not be priced (unknown, not zero). Does NOT compute income tax — use compute_payroll for gross-to-net take-home where supported. Pass api_key if you have one (instant card checkout at /pricing); otherwise the response explains how to pay via x402. The evaluation country is free to try (see list_series). Optional receipt (boolean, default false): on a paid success, include an Ed25519 answer receipt at no extra USDC. An answer receipt is not a series certified extract (GET /v1/certified/{country}/{series} is $0.10 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.

Input Schema

Name	Required	Description
`gross`	Yes	Gross pay in local currency
`period`	No	Period the gross covers (default month)
`api_key`	No	API key (bypasses x402; metered for invoicing)
`country`	Yes	ISO country code with a costed contribution schedule
`receipt`	No	Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.10; that SKU is not an MCP tool).
`contract`	No	Contract type where rates differ
`nationality`	No	Gulf nationality for pension reach
`subdivision`	No	Optional ISO 3166-2 regional schedule (e.g. CA-QC, DE-SN)
`childless_over_23`	No	Germany care surcharge
`children_under_25`	No	Germany per-child care reduction
`workplace_pension`	No	Auto-enrolment / PPK participation (default true)
`zusatzbeitrag_rate`	No	Germany sickness-fund supplement

Output Schema

Name	Required	Description
`basis`	No
`error`	No	Present on a free refusal or error; no charge
`status`	No	Answer status, e.g. computed or an honest no-answer status
`country`	No
`receipt`	No	Ed25519 answer receipt when receipt=true on a paid success
`question`	No
`no_charge`	No
`price_usd`	No
`disclaimer`	No
`how_to_pay`	No
`provenance`	No	Cited official sources behind the answer
`bind_series`	No
`explanation`	No
`label_basis`	No	Inputs and the rule ids that produced the two labels
`x_next_bind`	No
`http_endpoint`	No
`coverage_label`	No	How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules
`confidence_label`	No	Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules
`payment_required`	No	true when the call needs payment; how_to_pay explains x402 or card

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 17, 2026

changedInput schema / properties / receipt / description

Previous value: -"Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool)."New value: +"Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.10; that SKU is not an MCP tool)."

removedOutput schema / properties / label_basis / properties / source_type / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / label_basis / properties / source_type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / label_basis / properties / verification_age_days / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / label_basis / properties / verification_age_days / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed3 schema fields changedOct 13, 2026

addedOutput schema / properties / confidence_label

Added value: +{
+  "description": "Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules",
+  "enum": [
+    "high",
+    "medium",
+    "low"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / coverage_label

Added value: +{
+  "description": "How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules",
+  "enum": [
+    "ready",
+    "partial",
+    "gap"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / label_basis

Added value: +{
+  "additionalProperties": {},
+  "description": "Inputs and the rule ids that produced the two labels",
+  "properties": {
+    "confidence_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "coverage_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "inputs": {
+      "items": {},
+      "type": "array"
+    },
+    "rules": {
+      "type": "string"
+    },
+    "rules_version": {
+      "type": "string"
+    },
+    "source_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "stale": {
+      "type": "boolean"
+    },
+    "verification_age_days": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "Employee and employer statutory contributions with citations",
+  "properties": {
+    "basis": {},
+    "bind_series": {},
+    "country": {
+      "type": "string"
+    },
+    "disclaimer": {},
+    "error": {
+      "description": "Present on a free refusal or error; no charge"
+    },
+    "explanation": {},
+    "how_to_pay": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "http_endpoint": {
+      "type": "string"
+    },
+    "no_charge": {
+      "type": "boolean"
+    },
+    "payment_required": {
+      "description": "true when the call needs payment; how_to_pay explains x402 or card",
+      "type": "boolean"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provenance": {
+      "description": "Cited official sources behind the answer"
+    },
+    "question": {},
+    "receipt": {
+      "description": "Ed25519 answer receipt when receipt=true on a paid success"
+    },
+    "status": {
+      "description": "Answer status, e.g. computed or an honest no-answer status",
+      "type": "string"
+    },
+    "x_next_bind": {}
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 25, 2026

addedInput schema / properties / receipt

Added value: +{
+  "default": false,
+  "description": "Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool).",
+  "type": "boolean"
+}

AddedSep 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent/no-destructive profile, but the description adds materially new behavior: it is PAID ($0.05), needs api_key or x402 payment, returns an explicit refused list where schemes are 'unknown, not zero', and explains receipt emission on paid successes only. These auth/payment and output-semantics disclosures are value beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and payment constraint are front-loaded, but the paragraph sprawls into certified-extract SKU pricing, legal-advice disclaimers, and receipt verification that dilute the main message. Every sentence has some purpose, yet several are meta-documentation that could be trimmed without loss for tool selection.

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 an output schema present and 100% schema coverage, return values need not be explained; the description still adds the refused-list semantics, payment paths, and receipt behavior needed to call it correctly. The only real omission is that routing language references compute_payroll, which is not a listed sibling.

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 100%, so parameters are already documented; the description's receipt explanation closely mirrors the schema's own receipt description rather than adding new meaning. It mentions api_key usage but not the remaining ten parameters, so it neither compensates nor detracts — baseline 3 is right when the schema does the heavy lifting.

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?

States a specific verb and resource (prices statutory contributions on both employer and employee sides for a gross salary) and describes the returned line-by-line amounts plus a refused list. It explicitly carves out what it does NOT do relative to compute_income_tax/compute_payroll, so an agent can separate it from sibling tax tools.

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?

Gives clear routing: 'Does NOT compute income tax — use compute_payroll for gross-to-net take-home.' It also tells the agent how to preview for free via list_series and how to pay. It stops short of a full when-not matrix and routes to a tool (compute_payroll) not present in the sibling list.

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

All reference-data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?