Skip to main content
Glama
Sign In
ai-act-mcp

ai-act-mcp

by a2welt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

classify_risk

Determine the EU AI Act risk tier (prohibited, high, limited, or minimal) for an AI system by describing its purpose and impact. Uses cited articles and Annex III categories for informational triage.

Instructions

Classify an AI system under the EU AI Act risk tiers (prohibited / high / limited / minimal) from a plain-English description of what it does and who it affects. Returns the likely tier with cited articles and Annex III categories. Informational triage, not legal advice.

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": {
      "description": "<description>"
    },
    "name": "classify_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYesWhat the AI system does, its purpose, and who it affects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description adequately discloses what the tool returns (likely tier with cited articles and Annex III categories) and that it is not legal advice. It does not mention any side effects, but the tool is read-only by nature.

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 concise sentences, front-loading the purpose and input/output, with a caveat in the second sentence. No wasted words.

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 simple input and no output schema, the description sufficiently covers the input format, output content, and caveat. It could be improved by mentioning the classification is based on the description alone, but it is largely 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 coverage is 100% for the single parameter 'description'. The description's mention of 'plain-English description' adds slight reinforcement but no significant new meaning beyond the schema's own description.

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 EU AI Act risk tiers using a plain-English description, which is specific and distinguishes it from sibling tools like check_obligations or next_deadlines.

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?

It explicitly mentions the input is a plain-English description of the AI system and includes a caveat ('informational triage, not legal advice'). However, it does not explicitly state when not to use it or compare to alternatives, though the context is clear.

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

Deploy Server

Other Tools