Skip to main content
Glama

ThinkNEO Control Plane

by ai.thinkneo
OverviewDiscussionsAdmin

thinkneo_compliance_generate

Read-onlyIdempotent

Generate a compliance report for regulatory frameworks (EU AI Act, ISO 42001, SOC2, NIST). Exports from live audit data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format: ndjson or csvndjson
frameworkNoFramework: eu-ai-act, iso-42001, soc2, nisteu-ai-act
workspaceNoWorkspace identifierdefault

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / format / default
      Previous value: -"json"New value: +"ndjson"
    • changedInput schema / properties / format / description
      Previous value: -"Output format: json, csv, cef"New value: +"Output format: ndjson or csv"
  2. Changed6 schema fields changed
    • removedInput schema / properties / days
      Removed value: -{
-  "default": 30,
-  "description": "Number of days to include in the report (default 30, max 365)",
-  "title": "Days",
-  "type": "integer"
-}
    • addedInput schema / properties / format
      Added value: +{
+  "default": "json",
+  "description": "Output format: json, csv, cef",
+  "title": "Format",
+  "type": "string"
+}
    • addedInput schema / properties / framework / default
      Added value: +"eu-ai-act"
    • changedInput schema / properties / framework / description
      Previous value: -"Regulatory framework: 'lgpd', 'iso_42001', or 'eu_ai_act'"New value: +"Framework: eu-ai-act, iso-42001, soc2, nist"
    • addedInput schema / properties / workspace
      Added value: +{
+  "default": "default",
+  "description": "Workspace identifier",
+  "title": "Workspace",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "framework"
-]
  3. Added

TDQS

A3.8/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 clear. The description adds context about the data source ('live audit data'), which is useful for understanding freshness, but it does not disclose other behavioral aspects like authentication requirements or rate limits. This is acceptable given the 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?

The description is two sentences, front-loaded with the action and resource, and contains no redundant information. Every word contributes meaning.

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 output schema exists, annotations are present, and the input schema is well-documented, the description covers the essential aspects: purpose, frameworks, and data source. It could mention the return format or pagination behavior, but the output schema likely covers that, making the description sufficiently complete.

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 three parameters. The description adds value by listing the valid frameworks for the 'framework' parameter, but it does not address 'format' or 'workspace' 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?

The description clearly states a specific action ('Generate a compliance report') and identifies the resource scope (regulatory frameworks: EU AI Act, ISO 42001, SOC2, NIST). It distinguishes itself from sibling tools like thinkneo_get_compliance_status (status vs report) and thinkneo_audit_export (export vs generate) through its focus on generating reports from live audit data.

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 when a compliance report is needed for one of the listed frameworks, and notes the data source is live audit data. However, it does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or prerequisites.

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

All ThinkNEO Control Plane 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