Skip to main content
Glama

Rekvira: EU regulation pinpoints for compliance AI

by com.rekvira
OverviewDiscussionsAdmin

Open a playbook or job

get_workflow
Read-onlyIdempotent

Full step-by-step playbook for one workflow id from list_workflows. Follow the named tools (search_regulation, read_unit, verify_citation, …) rather than summarising the playbook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAlias for workflow_id
nameNoAlias for workflow_id
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_idNoOptional trial_id from connect to read your private draft
workflow_idNoId from list_workflows, e.g. high-risk-triage

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

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context by stating that the output is a full step-by-step playbook and by instructing the agent to follow the referenced tools instead of summarising. This goes beyond the safety profile the annotations provide.

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 two sentences with no wasted words. It front-loads the core purpose and source, then gives a clear operational instruction. Every sentence earns its place.

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 read-only retrieval tool, the description sufficiently explains what is returned and how to use it. The lack of an output schema is partially offset by 'full step-by-step playbook', though the title's mention of 'job' is not addressed in the description. The schema covers the parameter details, so nothing critical is missing for invoking the tool.

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 schema already documents all five parameters, including aliases and the session/trial_id semantics. The description adds no parameter-level detail beyond referring to a workflow id from list_workflows, which is already stated in the schema. 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?

The description clearly identifies the tool as retrieving a full step-by-step playbook for a single workflow id, which is distinct from list_workflows. It names the resource ('playbook'), the source ('from list_workflows'), and the scope ('one workflow id'), making the tool's purpose immediately obvious.

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 implies the prerequisite of getting a workflow id from list_workflows and instructs the agent to follow the named tools rather than summarising the playbook. It does not explicitly state when not to use this tool or name a direct alternative, but the 'one workflow id from list_workflows' phrasing gives enough context to select it appropriately.

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