Skip to main content
Glama

Rekvira: EU regulation pinpoints for compliance AI

by com.rekvira
OverviewDiscussionsAdmin

Publish a private playbook

publish_workflow

Mark one of this trial_id private playbooks ready or draft. Publishing is private state only; it never adds content to the shipped library or another trial.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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()
publishedNotrue marks it ready in this trial; false returns it to draft
workflow_idNoId of your private workflow

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description is expected to add behavioral nuance. It does so by clarifying that the change is confined to 'private state only' and 'never adds content to the shipped library or another trial'. This explains the mutating effect's scope beyond the annotations, though it does not disclose return behavior or idempotency nuances.

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 a single, concise sentence that front-loads the core action and immediately states the important scope limitation. There is no fluff or repetition; every word adds value.

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?

For a simple mutation tool with 4 optional parameters and no output schema, the description adequately states the effect and its scope. However, it does not mention what the tool returns (e.g., a success message, updated workflow, or error), which would help an agent know what to expect. Given the absence of an output schema, the description could have filled this gap but does not.

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 each parameter already has a clear description (e.g., published: 'true marks it ready in this trial; false returns it to draft'). The tool description says 'Mark one of this trial_id private playbooks ready or draft', which somewhat reinforces the published parameter meaning but does not add new semantic information beyond 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 uses a specific verb ('Mark') and resource ('private playbook'), clearly stating the action and its effect ('ready or draft'). It also distinguishes itself from adding content to the shipped library, which separates it from sibling tools like save_workflow or any public-publish action. This goes beyond a mere restatement of the name or title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by stating 'Publishing is private state only', which suggests this tool is not for public distribution, but it does not explicitly contrast with siblings like save_workflow or delete_workflow, nor does it state when to use this tool versus alternatives. The context is clear but no explicit exclusions or comparisons are given.

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