eu-ai-act

ai_act_scope_check

Deterministisk screening af et AI-system/use-case mod EU AI Act: Annex III (høj-risiko-kategorier), Art 5 (forbudt praksis) og Art 50 (transparenssignaler). Regelbaseret nøgleordsscreening — ingen LLM. Output: vurdering, begrundelse, relevante artikler, frister og kildelinks. Generel information, ikke juridisk rådgivning. (Deterministic EU AI Act Annex III scope screening, Danish output.)

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": "ai_act_scope_check"
  }
}

Input Schema

Name	Required	Description
`sector`	No	Valgfrit: sektor, fx HR, fintech, energi
`purpose`	No	Valgfrit: formål med systemet
`description`	Yes	Beskrivelse af AI-systemet eller use-casen (dansk eller engelsk)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A3.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it states the method is deterministic, rule-based keyword screening with no LLM, discloses that output is Danish, lists the returned fields, and adds a 'not legal advice' disclaimer. It still omits permission/auth needs and any accuracy or coverage caveats beyond the disclaimer.

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?

Dense but front-loaded: scope and method come first, output and disclaimer last. The trailing parenthetical English gloss is slightly redundant with the Danish text, but it usefully anchors the tool for non-Danish agents, so it earns its place.

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?

There is no output schema, yet the description enumerates the return contents (assessment, reasoning, relevant articles, deadlines, source links), which is what the agent needs to interpret results. Combined with the method and language disclosures, the definition is nearly complete for a 3-parameter screening tool.

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% for all three parameters, so the schema already documents each field, its optionality and its length limits. The description adds nothing about parameter formats or how sector/purpose influence the screening, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (screening) and resource (AI system/use-case) and enumerates the exact scope it covers: Annex III, Art 5, Art 50. It is clearly distinguishable from verify_deliverable and eu_ai_act_facts, though it does not explicitly contrast itself with the overlapping sibling art50_transparency_check.

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

Usage Guidelines2/5

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

The description says what is screened but never says when to choose this tool over the alternatives, nor when not to. With art50_transparency_check as a sibling covering one of the same articles, an explicit routing rule is exactly what is missing here.

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

All eu-ai-act tools Inspect

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

Need Help?