Skip to main content
Glama
SonnyLabs

EU AI Act Compliance MCP Server

by SonnyLabs

determine_eu_ai_act_role

Identify your organization's role under the EU AI Act to know which compliance obligations apply. Input company details and AI activities to receive role definitions and applicable requirements.

Instructions

Determine which EU AI Act role(s) apply to your organization.

Different roles have different obligations under the EU AI Act. Understanding your role is CRITICAL to knowing which requirements apply.

Args: company_description: Brief description of your company/organization company_location: Country/region where company is based develops_ai_system: You develop AI systems or commission their development uses_ai_system: You use AI systems in your operations sells_ai_system: You sell or offer AI systems imports_to_eu: You bring AI systems from outside EU into EU market distributes_in_eu: You distribute/resell AI systems in EU integrates_ai_into_product: You integrate AI into physical products represents_non_eu_provider: You represent a non-EU AI provider in the EU under_own_name_or_trademark: AI system bears your name/trademark substantial_modification: You substantially modify existing AI systems change_intended_purpose: You change the intended purpose of AI systems

Returns: Role determination with definitions and applicable obligations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imports_to_euNo
uses_ai_systemNo
sells_ai_systemNo
company_locationYes
distributes_in_euNo
develops_ai_systemNo
company_descriptionYes
change_intended_purposeNo
substantial_modificationNo
integrates_ai_into_productNo
represents_non_eu_providerNo
under_own_name_or_trademarkNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full transparency burden. It discloses that the tool returns a role determination with definitions and obligations, implying a non-destructive analysis. However, it lacks details on validation, edge cases, or side effects, leaving room for ambiguity.

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?

The description is front-loaded with the purpose and organized into a clear parameter list. While it is somewhat lengthy due to 12 parameters, each line is informative. The 'CRITICAL' emphasis is slightly extraneous but does not detract from overall structure.

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 complexity of 12 parameters and existence of an output schema, the description covers all inputs and output expectations. It doesn't specify constraints like company_location format or whether at least one activity flag must be set, but the parameter explanations provide enough context for correct invocation.

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

Parameters5/5

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

The input schema has 0% description coverage, but the description provides a one-sentence explanation for each of the 12 parameters, adding significant meaning beyond the bare titles. This fully compensates for the schema gap and gives clear semantics.

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?

Description clearly states the tool determines EU AI Act roles for an organization, which is a specific verb+resource. It distinguishes from sibling tools like risk classification or labeling, making the purpose unambiguous.

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?

The description implies use when an organization needs to understand its obligations under the EU AI Act, and emphasizes role understanding as critical. However, it doesn't explicitly mention alternatives or when-not-to-use, but 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.

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/SonnyLabs/EU_AI_ACT_MCP'

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