Skip to main content
Glama

EU AI Act Explorer

by com.euaiactlaw
OverviewDiscussionsAdmin

assess_compliance

Read-onlyIdempotent

Run the EU AI Act compliance assessment: given the entity's answers (same decision tree as the interactive checker on euaiactlaw.com), returns the applicable roles, risk classification, full obligation list with legal basis and deadlines, and notes (e.g. Annex I Section B reduced regime, open-source GPAI exception, Art 27(3) NCA notification, distributor obligations under Art 24). Pass answers keyed by step id (E1, E2, S1, R1-R5, HR1-HR6, ...); E1 (roles) is required. Multi-select steps take arrays of option ids; single-choice steps take one option id.

Input Schema

NameRequiredDescriptionDefault
E1YesWhat is your role in relation to the AI system? Options: provider = Provider; deployer = Deployer; distributor = Distributor; importer = Importer; product_manufacturer = Product Manufacturer; auth_rep = Authorised Representative. Omit keys that do not apply to your scenario.
E2NoDo you or any downstream entity make any of these modifications? Options: rename = Putting a different name or trademark on the system; repurpose = Modifying the intended purpose of a system already in operation; substantial_mod = Performing a substantial modification (Article 3(23)) to the system; none = None of the above. Omit keys that do not apply to your scenario.
E3NoDoes your product integrate an AI system and meet either criterion? Options: ai_with_product = AI system placed on the market together with the product under manufacturer name/trademark; ai_after_product = AI system put into service under manufacturer name/trademark after product placed on market; none = None of the above. Omit keys that do not apply to your scenario.
R1NoDoes your AI model meet any systemic risk criteria? (GPAI only) Options: high_flops = High impact capabilities (trained with cumulative compute >10²⁵ FLOPs); commission_decision = Commission has decided the model has high capabilities or impact (Annex XIII criteria); none = None of the above (or this is not a GPAI model). Omit keys that do not apply to your scenario.
R2NoDoes your system or use-case fall within any exclusion category? Options: military = AI systems developed and used exclusively for military purposes; third_country_law = Public authorities / international organisations in third countries using AI for law enforcement or judicial cooperation; research = AI research and development activity (not yet placed on market); open_source = AI components provided under free and open-source licences; personal_use = Purely personal, non-professional activity by a natural person; none = None of the above. Omit keys that do not apply to your scenario.
R3NoDoes your system perform any prohibited AI practices? Options: subliminal = Subliminal techniques, manipulation, or deception; vulnerable_exploit = Exploiting vulnerabilities of specific groups; biometric_categorisation_prohibited = Biometric categorisation to infer sensitive attributes; social_scoring = Social scoring — evaluating or classifying persons based on social behaviour; predictive_policing = Predictive policing based solely on profiling or personality traits; facial_scraping = Untargeted scraping of facial images from internet/CCTV to expand databases; emotion_recognition_prohibited = Emotion recognition in workplace or educational institutions; realtime_rbi = Real-time remote biometric identification in publicly accessible spaces for law enforcement; nonconsensual_intimate = Generating or manipulating non-consensual intimate material or child sexual abuse material; none = None of the above. Omit keys that do not apply to your scenario.
R4NoDoes your system perform any transparency-triggering functions? Options: deepfake = Generating or manipulating image/audio/video constituting a deep fake; public_interest_text = Generating or manipulating text published for matters of public interest (e.g., news); emotion_biometric = Emotion recognition or biometric categorisation (non-prohibited); natural_persons = Interacting directly with natural persons (e.g., chatbot); synthetic_content = Generating synthetic audio, image, video, or text content; none = None of the above. Omit keys that do not apply to your scenario.
R5NoAre you a body governed by public law, or a private entity providing public services, or operating in insurance/banking? Options: yes = Yes — public law body, public service provider, or insurance/banking entity; no = No — private entity not providing public services and not in insurance/banking. Omit keys that do not apply to your scenario.
S1NoDo you meet any of the following criteria for EU AI Act applicability? Options: placing_eu = I am placing on the market or putting into service AI systems in the EU; gpai_eu = I am placing on the market General Purpose AI (GPAI) models in the EU; established_eu = I am established or located within the EU; importer_eu = I am an importer placing on the EU market a system bearing a non-EU entity name; distributor_eu = I am a distributor making an AI system available on the EU market; output_eu = My AI system's output is used in the EU; none = None of the above. Omit keys that do not apply to your scenario.
HR1NoDoes your AI system fall within any Annex I, Section B categories? Options: aviation_security = Civil aviation security; motor_type_approval = Motor vehicles type approval; machinery = Machinery; vehicles_two_three = Two/three-wheel vehicles and quadricycles; agri_vehicles = Agricultural and forestry vehicles; marine = Marine equipment; rail = Interoperability of rail systems; motor_vehicles = Motor vehicles and their trailers; civil_aviation = Civil aviation; none = None of the above. Omit keys that do not apply to your scenario.
HR2NoDoes your AI system fall within any Annex I, Section A categories? Options: toys = Toys; recreational = Recreational craft & personal watercraft; lifts = Lifts and safety components of lifts; atex = Equipment for potentially explosive atmospheres; radio = Radio equipment; pressure = Pressure equipment; cableway = Cableway installations; ppe = Personal protective equipment; gas = Appliances burning gaseous fuels; medical = Medical devices; ivd = In vitro diagnostic medical devices; none = None of the above. Omit keys that do not apply to your scenario.
HR3NoIs your product required to undergo third-party conformity assessment under the applicable EU laws? Options: yes = Yes — third-party conformity assessment is required; no = No — manufacturer self-declaration or no third-party assessment required. Omit keys that do not apply to your scenario.
HR4NoDoes your AI system fall within any Annex III high-risk categories? Options: biometrics = Biometrics; critical_infra = Critical infrastructure; education = Educational and vocational training; employment = Employment, workers management, self-employment access; essential_services = Access to essential private/public services and benefits; law_enforcement = Law enforcement; migration = Migration, asylum, border control; justice = Administration of justice and democratic processes; none = None of the above. Omit keys that do not apply to your scenario.
HR5NoDoes your AI system pose a significant risk of harm to health, safety, or fundamental rights? Options: yes = Yes — poses significant risk (or system performs profiling of natural persons); no = No — meets one of the Art 6(3) derogation conditions. Omit keys that do not apply to your scenario.
HR6NoDoes your product include an AI system as a "safety component" AND fall within Annex I, Section A categories? Options: toys = Toys; recreational = Recreational craft & personal watercraft; lifts = Lifts and safety components of lifts; atex = Equipment for potentially explosive atmospheres; radio = Radio equipment; pressure = Pressure equipment; cableway = Cableway installations; ppe = Personal protective equipment; gas = Appliances burning gaseous fuels; medical = Medical devices; ivd = In vitro diagnostic medical devices; none = None of the above. Omit keys that do not apply to your scenario.

Output Schema

NameRequiredDescriptionDefault
routeNo
groupsNo
sourceNo
statusesYes
terminalYes
obligationsYes
checker_linkNo
obligation_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive operation. The description adds useful behavioral context: it discloses that the tool follows the same decision tree as the interactive checker and returns roles, risk classification, obligations, deadlines, and special-case notes such as the Annex I Section B reduced regime and open-source GPAI exception.

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 front-loaded with purpose and output scope, followed by concise input conventions. Despite being a single paragraph, every sentence earns its place for a complex 15-parameter assessment tool, and the parenthetical examples clarify special-case outputs without wasting space.

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?

The tool is complex, with 15 parameters and an output schema, but the description supplies the essential context an agent needs: what the assessment returns, how to key answers, which parameter is required, and how array versus scalar steps work. The output schema and annotations cover the remaining structured details.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents each answer key and its enum values. The description adds meaningful input mechanics beyond the schema: answers must be keyed by step id, E1 is required, multi-select steps use arrays of option ids, and single-choice steps use one option id.

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 states a specific verb and resource: 'Run the EU AI Act compliance assessment.' It also summarizes the outputs (roles, risk classification, obligations with legal basis and deadlines, and notes), making the tool's function clear without needing the schema.

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 gives clear usage context: it is used when you have the entity's answers and need a compliance assessment. It specifies that E1 is required and how to pass multi-select versus single-choice answers. It does not explicitly compare against sibling retrieval tools like get_obligations, but the assessment context is clear.

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 Explorer toolsInspect
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