Ansvar: EU Compliance & Legal Intelligence

List Coverage

list_coverage

Read-only

Show which countries, frameworks, and legal domains are available. Use this BEFORE calling search when the user's topic doesn't name a jurisdiction (e.g., 'what does the law say about consumer protection'); then present the returned jurisdictions to the user or ask which applies. Examples: • 'Which countries do you cover?' → list_coverage() • 'Do you have German law?' → list_coverage(jurisdiction='DE') • 'What jurisdictions for NIS2?' → list_coverage(domain='cybersecurity') • 'Which countries have drone law?' → list_coverage(domain='aviation') (also accepts 'drone' / 'uas') • 'Which countries have court decisions?' → list_coverage(content_kind='court-decisions') Returns a jurisdictions array (each with code, name, region, laws, provisions, domains, content_kinds, counts_complete, and uncounted_sources) plus framework and source listings. An incomplete-count row also carries coverage_note explaining why. NOTE: laws/provisions are WHOLE-JURISDICTION corpus totals — the response's count_scope is whole_jurisdiction. Under a domain filter the jurisdiction list is narrowed to that domain but the counts are NOT domain-scoped; do not report them as a per-domain count. The domain-specific signal is the (domain-filtered) sources/frameworks.

Input Schema

TableJSON Schema

Name	Required	Description
`domain`	No	Legal domain to narrow the jurisdiction list to, such as 'cybersecurity' or 'aviation' ('drone' and 'uas' are accepted for the latter, 'telecom' for 'telecommunications-media'). The law and provision counts stay whole-jurisdiction; the domain-scoped signal is the returned sources and frameworks.
`region`	No	Geographic region to narrow the jurisdiction list to, such as 'europe'. Empty returns every region.
`content_kind`	No	Kind of legal text to narrow the jurisdiction and source lists to: 'statute', 'court-decisions', 'preparatory-works' or 'disciplinary-decisions'. Frameworks are not classified by kind. Not combinable with jurisdiction (the single-jurisdiction view lists its content_kinds). An unknown value is an error listing the valid values.
`jurisdiction`	No	ISO-2 code to report on alone, such as DE. Empty returns every jurisdiction in scope.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / content_kind

Added value: +{
+  "default": "",
+  "description": "Kind of legal text to narrow the jurisdiction and source lists to: 'statute', 'court-decisions', 'preparatory-works' or 'disciplinary-decisions'. Frameworks are not classified by kind. Not combinable with jurisdiction (the single-jurisdiction view lists its content_kinds). An unknown value is an error listing the valid values.",
+  "title": "Content Kind",
+  "type": "string"
+}

changedInput schema / properties / domain / description

Previous value: -"Legal domain to narrow the jurisdiction list to, such as 'cybersecurity' or 'aviation' ('drone' and 'uas' are accepted for the latter). The law and provision counts stay whole-jurisdiction; the domain-scoped signal is the returned sources and frameworks."New value: +"Legal domain to narrow the jurisdiction list to, such as 'cybersecurity' or 'aviation' ('drone' and 'uas' are accepted for the latter, 'telecom' for 'telecommunications-media'). The law and provision counts stay whole-jurisdiction; the domain-scoped signal is the returned sources and frameworks."

Changed3 schema fields changedJul 31, 2026

addedInput schema / properties / domain / description

Added value: +"Legal domain to narrow the jurisdiction list to, such as 'cybersecurity' or 'aviation' ('drone' and 'uas' are accepted for the latter). The law and provision counts stay whole-jurisdiction; the domain-scoped signal is the returned sources and frameworks."

addedInput schema / properties / jurisdiction / description

Added value: +"ISO-2 code to report on alone, such as DE. Empty returns every jurisdiction in scope."

addedInput schema / properties / region / description

Added value: +"Geographic region to narrow the jurisdiction list to, such as 'europe'. Empty returns every region."

First observedJul 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly annotation, it discloses a non-obvious behavioral caveat: counts remain whole-jurisdiction and are not domain-scoped, so they must not be reported as per-domain counts. It also explains that incomplete rows carry coverage_note and that the domain-specific signal comes from sources/frameworks.

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?

The description is dense but every sentence earns its place: core purpose first, then usage timing, examples, return shape, and the critical count-scope caveat. The bulleted examples make scanning easy and the warning is clearly separated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only coverage tool with four optional parameters and an output schema, the description fully explains what the agent needs: when to call it, what each example query means, what the response contains, and an important interpretation pitfall. Nothing material is missing.

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?

The input schema already covers all four parameters at 100%, so the baseline is 3. The description adds value by showing exact parameter values through examples and by linking natural-language queries to parameter choices, while also reinforcing how domain affects the response semantics.

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 opens with a specific verb and resource ('Show which countries, frameworks, and legal domains are available') and is packed with concrete example user queries that map to tool invocations. It separates list_coverage from the sibling search tool by positioning it as the jurisdiction-discovery entry point.

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?

It explicitly says to call this BEFORE search when the user's topic doesn't name a jurisdiction, and gives five natural-language examples covering different parameters. This gives an agent clear decision criteria and names the relevant alternative (search).

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

All Ansvar: EU Compliance & Legal Intelligence 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.