Skip to main content
Glama
CSOAI-ORG

MEOK Fria Generator MCP

list_mandatory_triggers

Determine which situations make a Fundamental Rights Impact Assessment (FRIA) mandatory under EU AI Act Article 27(1).

Instructions

List the conditions that make a FRIA mandatory under Article 27(1).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `list_mandatory_triggers` tool handler function, decorated with @mcp.tool(). Returns the list of conditions triggering a mandatory FRIA under Article 27(1) of the EU AI Act.
    @mcp.tool()
    def list_mandatory_triggers() -> dict[str, Any]:
        """List the conditions that make a FRIA mandatory under Article 27(1)."""
        return {
            "mandatory_triggers": FRIA_MANDATORY_TRIGGERS,
            "regulatory_basis": "EU AI Act Reg (EU) 2024/1689 Article 27(1)",
        }
  • The @mcp.tool() decorator registers `list_mandatory_triggers` as an MCP tool on the FastMCP server instance.
    @mcp.tool()
  • The `FRIA_MANDATORY_TRIGGERS` constant — a list of trigger conditions referenced by the tool as its return data.
    FRIA_MANDATORY_TRIGGERS = [
        "Body governed by public law (Member State or EU institution)",
        "Private operator providing public services (e.g., recruitment for public-sector roles, education, healthcare)",
        "Deploying a high-risk AI system listed in Annex III",
        "Specifically: credit scoring (Annex III §5(b))",
        "Specifically: life/health insurance pricing (Annex III §5(c))",
    ]
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the tool lists conditions, but does not mention any constraints like read-only nature (assumed), data freshness, or lack of side effects. The description is minimal and lacks transparency beyond the basic function.

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 11-word sentence, entirely front-loaded with the key information. Every word is meaningful and there is no redundancy.

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 (no parameters, output schema exists), the description fully captures its purpose. The existence of an output schema means return values are documented separately. No additional context is needed for an agent to understand and invoke this tool correctly.

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?

The tool has no parameters, so schema coverage is trivially 100%. Following the rubric, 0 parameters warrants a baseline of 4. The description adds no parameter info because there are none, so this score reflects that no additional detail is needed.

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 tool lists conditions making a FRIA mandatory under Article 27(1). It uses a specific verb and resource, and distinguishes itself from sibling tools like 'is_fria_required' (which checks a specific case) and 'generate_fria_template' (which creates a document).

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?

No explicit guidance on when to use this tool vs alternatives is provided. However, the context of sibling tools suggests it is for obtaining a reference list. The purpose is clear enough that usage is implied, but no exclusion or alternative recommendations are given.

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/CSOAI-ORG/meok-fria-generator-mcp'

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