Skip to main content
Glama

Get Obligations by Role and Risk Level

euaiact_get_obligations
Read-onlyIdempotent

Retrieve EU AI Act compliance obligations tailored to your role (provider/deployer) and AI system risk level, including high-risk classification sources and GPAI model details.

Instructions

Returns specific compliance obligations for providers or deployers based on AI system risk level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleYesProvider or deployer role
risk_levelYesAI system risk level. Use 'gpai' for general-purpose AI model obligations (Art. 51-56).
high_risk_sourceNoFor high-risk systems, whether classification comes from Annex III/Art. 6(2), Annex I/Art. 6(1), or is unknownunknown
annex_iii_pointNoIf high_risk_source is annex_iii, the Annex III point number. Point 2 has special Art. 49/27 treatment.
gpai_model_placed_on_market_before_2025_08_02NoFor GPAI providers, whether the model was placed on the market before 2 August 2025, triggering the Art. 111(3) transition to 2 August 2027.
filter_keywordNoOptional keyword filter for obligations

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleYes
risk_levelYes
obligationsYes
penaltiesYes
lexbeam_urlNo
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that it returns obligations but does not elaborate on any non-obvious behaviors or constraints beyond what annotations and schema provide.

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 a single sentence with no wasted words. It is front-loaded with the action and resource.

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 output schema exists, parameter count is manageable, and annotations cover safety, the description is sufficient. It does not need to explain return values or additional context.

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%, so the schema fully documents each parameter. The tool description adds no new parameter meaning beyond stating that obligations are returned based on role and risk level.

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 verb 'returns' and resource 'compliance obligations', and specifies the key parameters (role and risk level). It distinguishes from siblings like euaiact_classify_system and euaiact_get_article.

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

Usage Guidelines3/5

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

The description implies usage by naming the parameters but does not explicitly state when to use this tool vs alternatives, nor when not to use it.

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/lexbeam-software/eu-ai-act-mcp'

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