Dutch-law-mcp

get_provision_at_date

Read-only

Retrieve a Dutch statute provision as it existed on a specific historical date. Use version history to get the exact text valid at that time, ideal for analyzing past legal situations or tracking changes.

Instructions

Retrieve a provision as it was at a specific historical date. Uses version history to return the text valid at that date. Essential for analyzing past legal situations or tracking how a provision changed over time. Set include_amendments=true to see the full amendment chain. Returns not_found if no version exists for that date. Use get_provision for the current version instead.

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": {
      "document_id": "<document_id>",
      "provision_ref": "<provision_ref>",
      "date": "<date>"
    },
    "name": "get_provision_at_date"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	ISO date to query the provision at (YYYY-MM-DD)
`document_id`	Yes	BWB-ID of the statute (e.g. "BWBR0005289")
`provision_ref`	Yes	Provision reference (e.g. "6:162" or "287")
`include_amendments`	No	Include amendment history records (default false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.2Aug 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral details: it uses version history, returns not_found if no version exists for the date, and the effect of include_amendments=true. No contradiction with annotations.

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?

Five concise sentences, each serving a distinct purpose: main action, rationale, optional parameter usage, error case, and alternative tool. No redundancy or filler.

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?

Comprehensive for a read-only tool: covers purpose, usage, error condition, and alternative. No output schema, but description indicates it returns the text valid at that date. Could mention response structure, but overall complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters, so baseline is 3. The description enhances semantics by elaborating on include_amendments (full amendment chain) and clarifying that date is for historical querying, adding value beyond the schema.

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?

The description clearly states the tool retrieves a provision at a specific historical date using version history. It specifies the verb 'Retrieve', the resource 'provision', and the temporal qualifier, distinguishing it from the sibling tool get_provision.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('analyzing past legal situations or tracking how a provision changed over time') and directs users to use get_provision for the current version. Additionally explains the include_amendments option for amendment chains.

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

Deploy Server