Skip to main content
Glama

Rekvira: EU regulation pinpoints for compliance AI

by com.rekvira
OverviewDiscussionsAdmin

List playbooks and jobs

list_workflows
Read-onlyIdempotent

Playbook library for compliance-officer workflows — high-risk triage, DORA ICT review, cross-reg scans, vendor questionnaires. Read a playbook before improvising a process. Pass trial_id from connect to list your own private drafts beside the shipped library. Then call get_workflow with workflow_id from this list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMost rows to return (default 10 on searches, max 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_idNoOptional trial_id from connect for this client private drafts
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. Changed2 schema fields changed
    • 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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by indicating the tool returns workflow_ids and that private drafts are included via trial_id. No contradiction with annotations, but it doesn't mention pagination, sorting, or the inclusion of 'jobs' as the title implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose—the list of compliance topics (high-risk triage, DORA ICT review, etc.) is nice context but not essential to function. It is structured with clear sentences but doesn't lead with a verb phrase, and the 'jobs' term from the title is absent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the main use case (listing playbooks, including private drafts) and points to the next step (get_workflow), but it omits 'jobs' entirely despite the title saying 'playbooks and jobs'. There is no output schema, so return details beyond workflow_id are unspecified, leaving some ambiguity.

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 all parameters already have descriptions. The description adds meaningful context for trial_id (from connect, private drafts) and ties the output to get_workflow via workflow_id, enriching the schema's basic parameter descriptions.

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?

The title clearly says 'List playbooks and jobs', and the description describes a playbook library with a list of workflow categories, implying a listing tool. It distinguishes itself from get_workflow by saying 'Then call get_workflow with workflow_id from this list.' However, the first sentence is a noun phrase rather than an explicit verb phrase, so it requires some inference.

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 gives practical context: 'Read a playbook before improvising a process' implies use this tool to discover available playbooks first. It also tells the agent to pass 'trial_id from connect' to see private drafts, which is important for the connect flow. It doesn't explicitly state exclusions or alternatives, but the context is clear.

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