Skip to main content
Glama
Sign In

Makuri Showcase (CogniLedger)

by io.github.Cogniledger
OverviewDiscussionsAdmin

get_compliance_matrix

Read-only

Returns Makuri's regulatory posture across EU AI Act, GDPR, GDPR-K (children data), COPPA, and ISO 42001 — as design intentions and operator self-assessment, NOT certified or audited compliance. No formal audit or conformity assessment has been performed. Statuses are design_aligned_unaudited, not_started, or not_applicable; there is deliberately no 'compliant' status. Use when the user asks about regulatory compliance, AI Act classification, or data protection for children — and present results as posture, not certification. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_compliance_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
regulationNoOptional filter to return a single regulation. When omitted, returns all five regulations in the matrix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing the epistemic status of the data: design intentions and operator self-assessment, no formal audit, and a deliberate absence of any 'compliant' status. This is exactly the caveat an agent must carry into its answer, and the status vocabulary is spelled out.

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?

Front-loaded with the resource and scoped well, with the audit disclaimer immediately following. It is slightly repetitive ('NOT certified or audited compliance' followed by 'No formal audit... has been performed') and the Makuri-disambiguation sentence, while useful, sits away from the core purpose.

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?

No output schema exists, and the description compensates by explaining what is returned (a five-regulation matrix) and the exact status vocabulary an agent will encounter. Combined with the readOnly annotation, an agent has everything needed to call and correctly frame the result.

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 coverage is 100% and the enum values are already documented in the schema, including the omit-to-return-all behavior. The description reinforces the five regulations covered but adds no syntax or semantic detail the schema lacks, so baseline 3 applies.

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 plus resource ('Returns Makuri's regulatory posture across EU AI Act, GDPR, GDPR-K, COPPA, and ISO 42001') with the exact scope enumerated. It is clearly distinguishable from siblings like get_safety_features or get_platform_info because the regulatory framing is unambiguous.

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?

Explicitly names trigger conditions ('user asks about regulatory compliance, AI Act classification, or data protection for children') and adds a presentation constraint ('present results as posture, not certification'). It does not explicitly contrast with a named sibling tool, which keeps it from a 5.

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

All Makuri Showcase (CogniLedger) 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