mcp-eu-sparql

search_by_date_range

Read-onlyIdempotent

Search EU legal acts by date range. Optionally filter by document type such as regulation, directive, or decision. Retrieve up to 50 results for a given period.

Instructions

Znajdz akty prawne UE z zakresu dat (po dacie dokumentu). Opcjonalnie filtruj po typie (REG=rozporzadzenie, DIR=dyrektywa, DEC=decyzja, RECO=zalecenie, OPIN=opinia). Maks. 50 wynikow na zapytanie. Uzyteczne do przegladu aktow z konkretnego okresu legislacyjnego.

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": {
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "search_by_date_range"
  }
}

Input Schema

Name	Required	Description
`date_from`	Yes	Data od (YYYY-MM-DD).
`date_to`	Yes	Data do (YYYY-MM-DD).
`document_type`	No	Skrot typu aktu: REG, DIR, DEC, RECO, OPIN. Pomin zeby objac wszystkie.
`lang`	No	ISO 639-3 jezyka tytulow. Domyslnie POL.
`limit`	No	Maks. liczba wynikow (1-50). Domyslnie 20.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds a useful behavioral constraint (max 50 results per query), which goes beyond annotations. It does not describe pagination or return format, but the annotations cover the core safety profile.

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?

Three sentences, each adding value. Purpose is front-loaded, options and limits are stated concisely. No unnecessary words.

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?

The tool has 5 parameters, 2 required, and no output schema. The description mentions max results and date range filtering, which is adequate. It does not explain ordering or error handling, but for a search tool with good annotations, this is nearly 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?

All 5 parameters are documented in the schema (100% coverage). The description adds minimal extra value: it expands the type abbreviations (e.g., REG=rozporzadzenie) and clarifies that omitting type covers all. The baseline of 3 is appropriate since schema descriptions are already complete.

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 finds EU legal acts within a date range, with optional type filtering. This distinguishes it from sibling tools 'search_by_celex' (by CELEX number) and 'search_cjeu' (Court of Justice documents).

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?

The description gives a clear use case (reviewing acts from a specific legislative period) and mentions optional filters and a maximum result limit. However, it does not explicitly state when not to use this tool or directly compare with siblings.

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

Deploy Server