Skip to main content
Glama
saidbazyar

sovereign-ai-act-mcp

by saidbazyar
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

lookup_article

Read-onlyIdempotent

Retrieve the exact text of any EU AI Act Article (1-113) by number, as published in the Official Journal. Supports 24 EU languages.

Instructions

Return the verbatim text of one specific EU AI Act Article (1–113), exactly as published in the Official Journal of the EU. USE THIS when the user names or asks for a known Article number (e.g. 'show me Article 6', 'what does Article 5 say'). For keyword/topic search across the whole law use search_eu_ai_act; to classify a system use classify_ai_system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesThe Article number to retrieve, an integer from 1 to 113. Examples: 5 (prohibited practices), 6 (high-risk classification), 9 (risk management), 14 (human oversight), 50 (transparency), 99 (penalties).
languageNoLanguage for the answer, as an ISO 639-1 code — one of the EU AI Act's 24 official languages (e.g. 'en' English, 'de' German, 'fr' French, 'es' Spanish, 'sv' Swedish). Defaults to 'en'.en

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds that the text is verbatim and from the Official Journal, enhancing transparency beyond annotations.

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?

Three clear, front-loaded sentences with no redundant information. Every sentence adds value: core function, usage guidance, alternatives.

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?

Given the simplicity of the tool and absence of output schema, the description fully explains what the tool returns and the constraints on input parameters. Sufficient for an AI agent to understand usage.

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 covers 100% of parameters with descriptions and examples. The tool description does not add new parameter information beyond what the schema provides, so baseline score 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?

Clearly states the tool returns verbatim text of a specific EU AI Act article, distinguishing it from sibling tools for keyword search or 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?

Explicitly specifies when to use this tool (user names an article number) and provides alternatives for other use cases, with clear references to sibling tools.

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/saidbazyar/sovereign-ai-act-mcp'

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