Skip to main content
Glama
Sign In

Rekvira: EU regulation pinpoints for compliance AI

by com.rekvira
OverviewDiscussionsAdmin

Search one regulation

search_regulation
Read-onlyIdempotent

Sign-in required: call connect(email) and connect_verify first (free, one email) unless this connection is already signed in. Search held regulation text. Returns pinpoints and excerpts, not summaries. Requires regulation id (e.g. eu-ai-act) and query string. limit, detail (compact|full) and max_chars bound the response. Then read_unit on the best pinpoints; verify_citation if checking someone else's cite.

Input Schema

NameRequiredDescriptionDefault
as_ofNoOptional date YYYY-MM-DD: answer with the wording in force on that date (default today). Amended provisions say which act gave them their wording
kindsNoOptional filter: recital, article, paragraph, annex, section
limitNoMost rows to return (default 10 on searches, max 50)
queryNoSearch terms in English (required)
detailNocompact (default: ~400-char excerpt around the match) | full (whole unit text)
max_charsNoCap on the response size in characters (default 8000)
regulationNoRegulation id from list_regulations (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional date YYYY-MM-DD: answer with the wording in force on that date (default today). Amended provisions say which act gave them their wording",
+  "title": "As Of"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "compact (default: ~400-char excerpt around the match) | full (whole unit text)",
+  "title": "Detail"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Most rows to return (default 10 on searches, max 50)",
+  "title": "Limit"
+}
    • addedInput schema / properties / max_chars
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Cap on the response size in characters (default 8000)",
+  "title": "Max Chars"
+}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behavior beyond them: a hard sign-in prerequisite, the nature of the return (excerpts not summaries), and the fact that limit/detail/max_chars bound response size. This is exactly the extra context the annotations cannot carry.

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?

Four tight sentences, front-loaded with the blocking prerequisite and then the purpose, then return shape, then the call chain. Every clause carries actionable information with no filler.

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?

With no output schema, the description still explains the return format (pinpoints and excerpts), the auth requirement, the bounding parameters, and the recommended next tools. Nothing an agent needs to call this 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 baseline is 3, but the description adds genuinely new value: a concrete regulation id example ('eu-ai-act'), a note that detail takes compact|full, and confirmation that the response size is bounded by limit/max_chars. It doesn't cover as_of or kinds, which the schema already documents.

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?

States a specific verb and resource ('Search held regulation text') and immediately clarifies the return shape ('pinpoints and excerpts, not summaries'). The requirement for a single regulation id implicitly separates it from the plural sibling search_regulations, so an agent can route without opening 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?

Explicitly states the prerequisite workflow ('call connect(email) and connect_verify first') and the follow-up routing ('Then read_unit on the best pinpoints; verify_citation if checking someone else's cite'). It names the alternative tools and the condition that selects each, leaving nothing to inference.

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

All Rekvira: EU regulation pinpoints for compliance AI 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