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. Search in the corpus's primary language (en), then fetch the hits in the user's language with the language argument of get_provision (a code, or a short list of codes for versions side by side).

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.8/5.0

Behavior5/5

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

Annotations cover only the safety profile (readOnly/openWorld/destructive). The description adds non-obvious behavioral context: the response shape (`jurisdictions` array and its fields), that `count_scope` is `whole_jurisdiction`, that counts are NOT domain-scoped under a `domain` filter, and that incomplete rows carry a `coverage_note`. These caveats directly prevent an agent from misreporting counts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core instruction, then examples that each earn their place by mapping a real user phrasing to a call. The trailing sentence about searching in 'en' and fetching with get_provision's `language` argument drifts into sibling-tool workflow and is mild scope creep for a coverage-listing tool.

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?

An output schema exists, so return values need not be documented, yet the description still summarizes them and flags the count-scoping caveat. For a read-only discovery tool with 100% schema coverage, nothing an agent needs to call it correctly 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?

Schema coverage is 100%, so the baseline is 3. The description earns extra credit by showing parameter values in worked examples (jurisdiction='DE', domain='cybersecurity', content_kind='court-decisions') and by restating the domain-vs-count scoping rule that governs how `domain` behaves.

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 concrete verb+resource: 'Show which countries, frameworks, and legal domains are available.' It immediately distinguishes itself from the sibling `search` by framing itself as a pre-search discovery step, so an agent can route between the two without inspecting schemas.

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?

Explicit when-to-use: 'Use this BEFORE calling `search` when the user's topic doesn't name a jurisdiction,' followed by the follow-up action ('present the returned jurisdictions to the user or ask which applies'). Five worked query-to-call examples remove any remaining ambiguity about invocation.

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.