Rekvira: EU regulation pinpoints for compliance AI

Who am I

whoami

Read-onlyIdempotent

Who is calling: tier, trial state, corpus load count. Pass trial_id from connect() to confirm the handle used for assessments and private workflows. After connect, call start_here or list_regulations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`session`	No	The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAuth) or a key.
`trial_id`	No	Optional trial_id from connect() — echoed when present

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

addedInput schema / properties / session

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAuth) or a key.",
+  "title": "Session"
+}

First observedSep 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark the call read-only and idempotent; the description adds the concrete output contents (tier, trial state, corpus load count) and the trial_id echo behavior. This is meaningful context beyond the structured fields without contradicting them.

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?

Two tight sentences, front-loaded with the call's purpose and followed by actionable parameter guidance. No filler or redundancy.

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 simple read-only identity check with rich annotations and fully documented parameters, the description covers what it returns and how to use it after connect. The absence of an output schema is mitigated by naming the returned fields, though a bit more on expected failure/auth scenarios could help.

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 coverage is 100% and both parameters already carry descriptions. The description adds the purpose of trial_id (confirming the handle for assessments/private workflows), but session is not elaborated beyond the schema, so the added value is modest.

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?

Description states the tool identifies the caller and reports tier, trial state, and corpus load count—clear verb and resource. It doesn't explicitly contrast with sibling tools, but the unique 'who is calling' scope distinguishes it.

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?

It instructs passing trial_id from connect() to confirm the handle and points to start_here or list_regulations as next steps, giving a clear post-connect usage context. It stops short of explicitly naming alternatives or when-not-to-use, but the workflow ordering is useful.

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

Resources

Need Help?