Skip to main content
Glama
CSOAI-ORG

MEOK Fria Generator MCP

list_charter_articles

Lists EU Charter of Fundamental Rights articles relevant to AI deployer FRIA for compliance assessment.

Instructions

List EU Charter of Fundamental Rights articles relevant to AI deployer FRIA.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `list_charter_articles` tool handler function. Decorated with @mcp.tool(), it returns the CHARTER_REFERENCE dictionary (EU Charter of Fundamental Rights articles relevant to FRIA).
    @mcp.tool()
    def list_charter_articles() -> dict[str, str]:
        """List EU Charter of Fundamental Rights articles relevant to AI deployer FRIA."""
        return CHARTER_REFERENCE
  • The `CHARTER_REFERENCE` constant dictionary that `list_charter_articles` returns. Contains 16 EU Charter articles (Art. 1, 7, 8, 11, 14, 15, 21, 23, 24, 25, 26, 31, 34, 35, 41, 47) mapped to their human-readable titles.
    CHARTER_REFERENCE = {
        "Art. 1": "Human dignity",
        "Art. 7": "Respect for private and family life",
        "Art. 8": "Protection of personal data",
        "Art. 11": "Freedom of expression and information",
        "Art. 14": "Right to education",
        "Art. 15": "Freedom to choose an occupation and right to engage in work",
        "Art. 21": "Non-discrimination",
        "Art. 23": "Equality between women and men",
        "Art. 24": "Rights of the child",
        "Art. 25": "Rights of the elderly",
        "Art. 26": "Integration of persons with disabilities",
        "Art. 31": "Fair and just working conditions",
        "Art. 34": "Social security and social assistance",
        "Art. 35": "Health care",
        "Art. 41": "Right to good administration",
        "Art. 47": "Right to an effective remedy and to a fair trial",
    }
  • The `charter_reference` key is also embedded within the generated FRIA template from `generate_fria_template`, referencing the same CHARTER_REFERENCE data.
    "charter_reference": CHARTER_REFERENCE,
    "review_schedule": {
  • The MCP server is initialized as a FastMCP instance (`mcp = FastMCP("meok-fria-generator")`). The tool is registered implicitly via the @mcp.tool() decorator on the handler function.
    mcp = FastMCP("meok-fria-generator")
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of disclosure. It only states that the tool lists articles relevant to AI deployer FRIA, but does not disclose that the operation is read-only, whether it requires authentication, or any side effects. Minimal behavioral context.

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 that directly states the tool's purpose with no wasted words. It is front-loaded and easy to parse.

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 tool has no parameters and a likely straightforward output (with an output schema present), the description is adequate. However, it could be improved by mentioning that the list covers all relevant articles without requiring input or by noting any dynamic vs static nature.

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?

There are no parameters (0 params, schema coverage 100%), so the baseline is 4. The description adds value by specifying the scope ('relevant to AI deployer FRIA'), which clarifies what articles are returned beyond an empty schema.

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 uses the specific verb 'List' and resource 'EU Charter of Fundamental Rights articles', and clearly limits the scope to those 'relevant to AI deployer FRIA'. This distinctively separates it from sibling tools like list_mandatory_triggers or map_to_edpb_dpia.

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 the tool is used during FRIA to retrieve relevant charter articles, but provides no explicit guidance on when to use it versus alternatives (e.g., list_mandatory_triggers). No when-not-to-use or prerequisite information is 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