Ansvar: EU Compliance & Legal Intelligence

Generate Report

generate_report

Read-only

Produce the final compliance report from a completed workflow. Use this when someone says 'generate the gap analysis report', 'I need the DPIA report as a document', or 'create the threat model output'. Refuses until every quality gate passes, returning the failing check and a hint. Returns a structured report with findings, citations, and recommendations. Pass format html, pdf, docx, or all to additionally receive branded rendered artifacts as short-lived download URLs in a sibling render key; render failures attach render_error and never drop the report JSON. Rendering is served by the document plane and starts at the premium tier; on free and solo an included run also returns html or pdf, and outside an included run free and solo receive the report as JSON. A format the caller's tier does not serve is refused explicitly rather than quietly downgraded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workflow_id": "<workflow_id>"
    },
    "name": "generate_report"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No	Artifacts to produce alongside the report JSON: 'json' (the default, JSON only), 'html', 'pdf', 'docx', or 'all'. Rendered artifacts come back as short-lived download URLs. The advertised enum is narrowed to what your tier serves, and a format your tier does not serve is refused rather than downgraded.	json
`workflow_id`	Yes	Id of the workflow run, as returned by start_workflow. Recover a lost id with list_workflows.
`include_report`	No	false returns only the delivery receipt (with its display_markdown), any rendered artifact links and the relay block; use it when your client limits tool output size. Default true returns the full report.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / include_report

Added value: +{
+  "default": true,
+  "description": "false returns only the delivery receipt (with its display_markdown), any rendered artifact links and the relay block; use it when your client limits tool output size. Default true returns the full report.",
+  "title": "Include Report",
+  "type": "boolean"
+}

Changed2 schema fields changedJul 31, 2026

addedInput schema / properties / format / description

Added value: +"Artifacts to produce alongside the report JSON: 'json' (the default, JSON only), 'html', 'pdf', 'docx', or 'all'. Rendered artifacts come back as short-lived download URLs. The advertised enum is narrowed to what your tier serves, and a format your tier does not serve is refused rather than downgraded."

addedInput schema / properties / workflow_id / description

Added value: +"Id of the workflow run, as returned by start_workflow. Recover a lost id with list_workflows."

First observedJul 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnly/openWorld/destructive flags, and the description adds substantial behavior beyond them: refusal semantics on failed gates with the failing check and hint, the sibling render key, render_error handling that never drops the report JSON, and tier-dependent rendering. It also states that an unserved format is refused explicitly rather than silently downgraded.

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

Conciseness4/5

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

Purpose is front-loaded and each sentence carries information, but the tier-rendering rules occupy two long sentences and restate the format enum behavior already present in the schema. Slightly redundant rather than bloated.

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

Completeness5/5

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

An output schema exists, yet the description still outlines the report shape, the render key, and error keys — enough for an agent to invoke the tool and interpret a refusal or a partial render. Nothing needed for correct invocation is missing.

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 the baseline is 3, but the description adds real meaning about the consequence of `format`: rendered artifacts arrive as short-lived URLs in a separate render key, and the accepted enum narrows per tier. It does not mention `include_report` or `workflow_id` recovery, which the schema already covers.

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?

Specific verb and resource — 'Produce the final compliance report from a completed workflow' — that no sibling tool (validate_claim, get_progress, start_workflow) could be confused with. It also names the concrete outputs (findings, citations, recommendations) an agent can expect.

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?

Gives explicit trigger phrases ('generate the gap analysis report', 'I need the DPIA report as a document') and a prerequisite (a completed workflow whose quality gates pass). It stops short of naming which sibling to use instead when the workflow is incomplete or when only validation is wanted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ansvar: EU Compliance & Legal Intelligence 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.