Skip to main content
Glama

Rekvira: EU regulation pinpoints for compliance AI

by com.rekvira
OverviewDiscussionsAdmin

List my assessments

list_assessments
Read-onlyIdempotent

List this trial_id's recorded assessments, newest first. Pass the trial_id from connect(). Use when resuming a multi-week DPIA or applicability review. Never invent rows for another trial.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows (1–100, default 50)
sessionNoThe `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_idNotrial_id returned by connect()
max_charsNoCap on the response size in characters (default 8000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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.2/5.0
Behavior4/5

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

Annotations already supply readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavior: newest-first ordering, limitation to recorded rows, and the guardrail 'Never invent rows for another trial.' No contradiction with annotations.

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 concise sentences, each earning its place: purpose, prerequisite, usage context, and a data-integrity guardrail. The core action is front-loaded and there is no filler.

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?

Given the rich annotations and 100% schema coverage, the description supplies the main missing invocation context: when to use it, what scope to pass, and the expectation not to fabricate rows. It could mention response shape or pagination, but those are not critical for correct selection and invocation.

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 description coverage is 100%, so the structured schema already documents all four parameters. The description repeats the trial_id source but adds no parameter meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

Clearly states a specific verb and resource: 'List this trial_id's recorded assessments, newest first.' The trial-scoped resource distinguishes it from sibling list_workflows and list_regulations, and from record_assessment. The title's 'my' is clarified to be trial-scoped rather than user-scoped.

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?

Provides an explicit use case ('when resuming a multi-week DPIA or applicability review') and a prerequisite ('Pass the trial_id from connect()'). It does not name sibling alternatives or describe when not to use it, so it falls just short of full routing guidance.

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