RPV Calculator

Get indexed rate table

get_rate_table

Read-onlyIdempotent

Returns every bracket of the procedural indemnity table for a court type (min/base/max in EUR), indexed for the given date. Pass the amount in dispute when the user mentions one, so the card can highlight its bracket.

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": {
      "court_type": "<court_type>"
    },
    "name": "get_rate_table"
  }
}

Input Schema

Name	Required	Description
`date`	No	Optional reference date (YYYY-MM-DD), usually the date of the judgment. Defaults to today. Uses the indexation in force on that date.
`amount`	No	Optional amount in dispute in EUR, to highlight its bracket. A number, or a Belgian-formatted string such as "12.500".
`locale`	No	Language of the card and the calculator link. Always set it to the language the user writes in (nl, fr, de or en; use "en" for any other language). Defaults to "nl".
`court_type`	Yes	Court/procedure type: "general" = General rate (art. 2 KB 26/10/2007): all courts and tribunals, including labour courts for e.g. employment-contract disputes. "voorzitter" = President of the Labour Court, proceedings under arts. 579 and 1017(2) Judicial Code (occupational accidents/diseases, social security). "arbeidsrechtbank" = Labour Court (arbeidsrechtbank / tribunal du travail), proceedings under arts. 579 and 1017(2) Judicial Code. "arbeidshof" = Labour Court of Appeal (arbeidshof / cour du travail), proceedings under arts. 579 and 1017(2) Judicial Code.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / amount

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Optional amount in dispute in EUR, to highlight its bracket. A number, or a Belgian-formatted string such as \"12.500\"."
+}

changedInput schema / properties / locale / description

Previous value: -"Language of the returned calculator link. Defaults to \"nl\"."New value: +"Language of the card and the calculator link. Always set it to the language the user writes in (nl, fr, de or en; use \"en\" for any other language). Defaults to \"nl\"."

First observedOct 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint false, and idempotentHint, covering the safety profile. The description adds that results are indexed to a date and that the amount highlights a bracket, but omits auth, rate limits, or error behavior.

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, front-loaded with the return content and followed by a focused usage tip. No redundant or filler text.

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 read-only table lookup with a fully described schema and safety annotations, the description covers purpose, output content, and the indexation/amount context. It omits any reference to sibling tools, which could help an agent route correctly, but is otherwise sufficient.

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 the schema already documents all four parameters including enums for court_type and locale. The description only reiterates the amount parameter's purpose, adding no new syntax or edge-case guidance.

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?

States a specific verb ('Returns') and resource ('every bracket of the procedural indemnity table') with clear scope ('for a court type', 'indexed for the given date'). It implicitly differentiates from calculate_rpv by returning all brackets rather than a computed amount, but does not name siblings explicitly.

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?

Provides a parameter-level guideline ('Pass the amount in dispute when the user mentions one'), but offers no overall when-to-use guidance or comparison to calculate_rpv / get_indexation_status. Usage is implied by the purpose.

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

All RPV Calculator 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?