Skip to main content
Glama
Sign In
mcp-eu-sparql

mcp-eu-sparql

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_cjeu

Read-onlyIdempotent

Search CJEU case law (judgments and orders) from EUR-Lex. Filter by date range and language to retrieve CELEX identifiers, titles, and direct links.

Instructions

Wyszukaj orzeczenia Trybunalu Sprawiedliwosci UE (CJEU) - wyroki (JUDG) i postanowienia (ORDER). Opcjonalnie zawez do zakresu dat. Zwraca CELEX (np. 62022CJ0252), date wydania, tytul (jezyk wg lang) i EUR-Lex URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_cjeu"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_fromNoData od (YYYY-MM-DD). Opcjonalna.
date_toNoData do (YYYY-MM-DD). Opcjonalna.
langNoISO 639-3 jezyka tytulow. Domyslnie POL.
limitNoMaks. liczba wynikow (1-50). Domyslnie 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, not destructive. Description adds that it returns specific fields, but does not disclose pagination, sorting, or filtering by type. Adequate but not rich.

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?

Single sentence, front-loaded with purpose, no wasted words. Highly concise and structured.

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?

Describes return values (CELEX, date, title, URL) since no output schema. Covers all parameters with descriptions. Missing details on sorting or default behavior, but sufficient for basic use.

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 covers all parameters with descriptions (100% coverage). Description adds no extra meaning beyond what schema provides, so baseline 3.

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 clearly states the tool searches CJEU judgments and orders, with optional date filtering, and lists returned fields. It distinguishes from sibling tools by being a general search, though it does not explicitly differentiate.

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?

Implies usage for general CJEU search with optional date range, but no guidance on when to use sibling tools (search_by_celex, search_by_date_range) or exclusions.

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

Deploy Server

Other Tools