Skip to main content
Glama

DataCastle EU Compliance & Customs

datacastle_check_ai_act_compliance

Evaluates enterprise AI architectures and logistics software against the EU AI Act (Regulation EU 2024/1689). Classifies risk tier (Prohibited, High-Risk, Transparency, Minimal), assesses Article 10 data governance compliance, and generates required technical documentation mandates.

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": {
      "systemDescription": "<systemDescription>"
    },
    "name": "datacastle_check_ai_act_compliance"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemRoleNoPrimary domain of the AI system.
systemDescriptionYesDetailed description of the AI system, autonomous agent, or model use case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the substantive outputs (risk tier, Article 10 assessment, documentation mandates), which tells the agent what analysis it performs. It does not say whether the tool is read-only, whether it retrieves external legal text, whether results are deterministic, or what form the generated documentation takes — meaningful gaps for a tool with no annotation coverage.

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?

A single dense sentence that front-loads the regulation and then enumerates the three analyses produced; nothing is padding. It is slightly run-on, packing classification, assessment, and documentation generation into one clause chain, but every clause earns its place.

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?

With no output schema and no annotations, the description must convey both behavior and return shape. It conveys the conceptual outputs but not their structure or format, and says nothing about limitations (e.g., whether it is legal advice, what happens with an unrecognized system description). Adequate for a two-parameter tool but leaves real gaps.

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% and the enum for systemRole is self-explanatory, so the schema does the heavy lifting. The description adds no parameter-level meaning (e.g., how detailed systemDescription should be, or how systemRole changes the analysis), so the 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?

Names a specific verb (Evaluates) and resource (enterprise AI architectures / logistics software) and pins it to a concrete regulation (EU AI Act 2024/1689). The three stated capabilities — risk-tier classification with named tiers, Article 10 data-governance assessment, and technical documentation mandates — make it unambiguous and clearly distinct from the sibling tools, which deal with customs documents, freight discrepancies, and TARIC codes.

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?

Usage is implied by the regulatory framing: an agent can infer this is the tool for EU AI Act compliance questions. However, there is no explicit when-to-use/when-not-to-use guidance, no mention of what inputs are expected beyond the schema, and no statement about how it relates to the sibling compliance/verification tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.