Skip to main content
Glama
CSOAI-ORG

EU AI Act Compliance MCP

classify_ai_risk

Classify AI systems into EU AI Act risk categories (prohibited, high-risk, limited-risk, minimal-risk) using a system description. Supports compliance assessment and gap analysis.

Instructions

Classify an AI system's risk level under the EU AI Act.

Takes a description of an AI system and returns its risk classification: prohibited, high-risk, limited-risk, or minimal-risk — per Article 5 (prohibited practices), Article 6 + Annex III (high-risk), Articles 50/52 (limited risk: transparency obligations), or minimal risk.

Includes all 8 Annex III high-risk areas and all Article 5 prohibited practices.

Args: description: A description of the AI system, its purpose, data used, and deployment context. caller: Identifier for rate limiting. tier: "free" (10 calls/day) or "pro" (unlimited, $29/mo).

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need to assess, audit, or verify compliance requirements. Ideal for gap analysis, readiness checks, and generating compliance documentation.

When NOT to use: Do not use as a substitute for qualified legal counsel. This tool provides technical compliance guidance, not legal advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYes
callerNoanonymous
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description discloses key behaviors: read-only, stateless, idempotent, rate limits per tier, and no authentication required for basic usage. It could detail api_key behavior but overall is thorough.

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

Conciseness2/5

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

The description is well-structured with sections but includes inaccurate parameter information (tier vs api_key), which wastes agent attention and harms clarity. It could be more concise by removing erroneous details.

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?

Given the complexity of EU AI Act classification, the description covers purpose, legal references, and behavior. However, it lacks details on the output format (even though an output schema exists) and contains a parameter mismatch, leaving gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description incorrectly describes a 'tier' parameter (free/pro) that does not exist in the input schema; the actual parameter is 'api_key' with no such tier options. This misleads the agent and fails to explain the api_key parameter's role.

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 the tool classifies AI systems under the EU AI Act into four risk categories and references specific articles. It differentiates from sibling tools like assess_penalties and audit_report by focusing on risk classification.

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

Usage Guidelines5/5

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

The description includes explicit 'When to use' and 'When NOT to use' sections, advising usage for compliance audits and warning against substituting for legal counsel. This provides clear contextual guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/eu-ai-act-compliance-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server