Skip to main content
Glama

Ansvar: EU Compliance & Legal Intelligence

by eu.ansvar
OverviewDiscussionsAdmin

Discover Eu Legislation

discover_eu_legislation
Read-only

Find EU legal acts by CELEX/ELI identifier, official title, reviewed alias, or LEXICAL match on title and EuroVoc labels (not semantic); filter by EuroVoc topic id or label, Ansvar sector, document type and availability. Returns bounded candidates with per-edition currency state and hold reasons, a framework crosswalk to eu-regulations where the same act is keyed there, and exact search/lookup hints.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNoCELEX or ELI identifier, official title fragment, or a short concept phrase. Optional when at least one of topics/sectors/document_types/availability is given (filter-only discovery); a call with neither query nor filters refuses with reason=empty_request. Matching is LEXICAL, not semantic: exact CELEX/ELI, exact official title, reviewed alias, then every query token within ONE title or within ONE EuroVoc label (pref or alt) of the work — never across labels. A short candidate list is a lexical result, not a coverage claim.
cursorNo
expandNowith a single-work query (celex_exact/eli_exact hit) return the FULL editions or related list for that work instead of the bounded default
topicsNoEuroVoc concept ids — the last path segment of the concept URI: numeric legacy ids or the hashed `c_<hex>` ids EuroVoc uses for newer concepts (release 4.24 carries both) — OR English EuroVoc labels. A label resolves by exact NFKC case-insensitive match on a pref label, else on an alt label; an unresolved label refuses unknown_filter_value naming up to 20 candidate {id, label} pairs whose label contains every token of the input; a label matching more than one concept refuses ambiguous_topic listing them. applied_filters.topics echoes the RESOLVED ids (the cursor binds those) and disclosures records each label→id resolution. Exact, OR within the list, AND with the other axes
sectorsNoAnsvar sector/domain ids; OR within the list, AND with the other axes
availabilityNo
document_typesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"CELEX or ELI identifier, official title fragment, or a short concept phrase. Optional when at least one of topics/sectors/document_types/availability is given (filter-only discovery); a call with neither query nor filters refuses with reason=empty_request."New value: +"CELEX or ELI identifier, official title fragment, or a short concept phrase. Optional when at least one of topics/sectors/document_types/availability is given (filter-only discovery); a call with neither query nor filters refuses with reason=empty_request. Matching is LEXICAL, not semantic: exact CELEX/ELI, exact official title, reviewed alias, then every query token within ONE title or within ONE EuroVoc label (pref or alt) of the work — never across labels. A short candidate list is a lexical result, not a coverage claim."
    • changedInput schema / properties / topics / description
      Previous value: -"EuroVoc concept ids — the last path segment of the concept URI: numeric legacy ids or the hashed `c_<hex>` ids EuroVoc uses for newer concepts (release 4.24 carries both); exact, OR within the list, AND with the other axes"New value: +"EuroVoc concept ids — the last path segment of the concept URI: numeric legacy ids or the hashed `c_<hex>` ids EuroVoc uses for newer concepts (release 4.24 carries both) — OR English EuroVoc labels. A label resolves by exact NFKC case-insensitive match on a pref label, else on an alt label; an unresolved label refuses unknown_filter_value naming up to 20 candidate {id, label} pairs whose label contains every token of the input; a label matching more than one concept refuses ambiguous_topic listing them. applied_filters.topics echoes the RESOLVED ids (the cursor binds those) and disclosures records each label→id resolution. Exact, OR within the list, AND with the other axes"
    • changedInput schema / properties / topics / items / pattern
      Previous value: -"^(?:[0-9]{1,6}|c_[0-9a-f]{4,16})$"New value: +"^(?:[0-9]{1,6}|c_[0-9a-f]{4,16}|\\S(?:.{0,118}\\S)?)$"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses bounded results, per-edition currency state, hold reasons, crosswalk behavior, and exact search/lookup hints. The explicit warning that lexical matches are not coverage claims is especially valuable for setting agent expectations.

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 well-structured, leading with the core purpose and then adding high-value caveats and return characteristics. No sentences are wasted, and the most decision-relevant information appears first.

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?

For a tool with no output schema, the description covers returns at a useful level: bounded candidates, currency state, hold reasons, crosswalk, and hints. It also documents refusal and ambiguity cases in the parameter descriptions. A minor gap is the lack of explicit cursor/pagination semantics, though the cursor parameter exists in the schema.

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 schema descriptions for query, topics, sectors, and expand already provide detailed semantics, and the main description adds the lexical matching model and bounded-result behavior. Undocumented parameters like availability, document_types, cursor, and limit are less explained, but their enums and constraints offer partial self-documentation.

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: "Find EU legal acts" by CELEX/ELI identifier, official title, reviewed alias, or lexical match. It clearly distinguishes this from generic siblings like search and search_by_product by naming EU-specific identifiers, EuroVoc labels, and Ansvar sectors.

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 and query parameter explicitly explain when the tool can be called: query-only, filter-only, or both, and that omitting both refuses with empty_request. It also warns that matching is lexical, not semantic, and that a short candidate list is not a coverage claim. However, it does not explicitly name sibling alternatives or state when to prefer another tool.

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 toolsInspect
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.

Resources