Skip to main content
Glama
CSOAI-ORG

CSRD Compliance MCP

enforcement_status

Check the current CSRD enforcement phase-in schedule and Member State transposition status to assess compliance requirements.

Instructions

Current CSRD enforcement phase-in schedule + Member State transposition status.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need to assess, audit, or verify compliance requirements. Ideal for gap analysis, readiness checks, and generating compliance documentation.

When NOT to use: Do not use as a substitute for qualified legal counsel. This tool provides technical compliance guidance, not legal advice.

Args: api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The enforcement_status function is a tool decorated with @mcp.tool() that returns CSRD enforcement phase-in schedule, member state transposition status, current date, and omnibus simplification proposal info as JSON. It is read-only, idempotent, and takes an optional api_key parameter.
    @mcp.tool()
    def enforcement_status(api_key: str = "") -> str:
        """Current CSRD enforcement phase-in schedule + Member State transposition status.
    
        Behavior:
            This tool is read-only and stateless — it produces analysis output
            without modifying any external systems, databases, or files.
            Safe to call repeatedly with identical inputs (idempotent).
            Free tier: 10/day rate limit. Pro tier: unlimited.
            No authentication required for basic usage.
    
        When to use:
            Use this tool when you need to assess, audit, or verify compliance
            requirements. Ideal for gap analysis, readiness checks, and generating
            compliance documentation.
    
        When NOT to use:
            Do not use as a substitute for qualified legal counsel. This tool
            provides technical compliance guidance, not legal advice.
    
        Args:
            api_key (str): The api key to analyze or process.
    
        Behavioral Transparency:
            - Side Effects: This tool is read-only and produces no side effects. It does not modify
              any external state, databases, or files. All output is computed in-memory and returned
              directly to the caller.
            - Authentication: No authentication required for basic usage. Pro/Enterprise tiers
              require a valid MEOK API key passed via the MEOK_API_KEY environment variable.
            - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are
              included in responses (X-RateLimit-Remaining, X-RateLimit-Reset).
            - Error Handling: Returns structured error objects with 'error' key on failure.
              Never raises unhandled exceptions. Invalid inputs return descriptive validation errors.
            - Idempotency: Fully idempotent — calling with the same inputs always produces the
              same output. Safe to retry on timeout or transient failure.
            - Data Privacy: No input data is stored, logged, or transmitted to external services.
              All processing happens locally within the MCP server process.
        """
        now = datetime.now(timezone.utc)
        return json.dumps({
            "directive": "Directive (EU) 2022/2464 (CSRD) + Directive (EU) 2013/34/EU (Accounting Directive, amended)",
            "standards": "Commission Delegated Regulation (EU) 2023/2772 — ESRS Set 1",
            "phases": ENFORCEMENT_PHASES,
            "current_date_utc": now.isoformat(),
            "immediate_priority": "~12,000 companies with first reports due in 2025-2026. Double materiality + ESRS gap analysis takes 9-12 months.",
            "omnibus_simplification_proposal": "Commission proposed 'omnibus simplification package' in 2025 — may delay phase-in for medium-large entities. Monitor official EUR-Lex updates.",
        }, indent=2)
  • server.py:461-462 (registration)
    The @mcp.tool() decorator on enforcement_status registers it as an MCP tool in the FastMCP server.
    @mcp.tool()
    def enforcement_status(api_key: str = "") -> str:
  • ENFORCEMENT_PHASES is a list of dictionaries defining the CSRD phase-in schedule for FY2024-FY2028, used as the 'phases' value in enforcement_status's output.
    ENFORCEMENT_PHASES = [
        {"fy": "2024", "who": "Large public-interest entities (>500 employees)", "report_due": "2025"},
        {"fy": "2025", "who": "Other large companies (meeting 2 of: >250 employees, €50M turnover, €25M balance sheet)", "report_due": "2026"},
        {"fy": "2026", "who": "Listed SMEs", "report_due": "2027 (with possible 2-year opt-out to 2028)"},
        {"fy": "2028", "who": "Non-EU parents with EU turnover >€150M + EU subsidiary/branch", "report_due": "2029"},
    ]
Behavior5/5

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

Since no annotations are provided, the description carries the full burden. It thoroughly discloses read-only, stateless, idempotent behavior, rate limits, authentication needs, error handling, and data privacy practices—far exceeding typical annotation coverage.

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 well-organized with sections, but there is redundancy between the 'Behavior' and 'Behavioral Transparency' sections, which repeat several points. The 'Args' section is brief. Overall, it is reasonably concise but could be tightened.

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?

The description covers purpose, usage, behavior, and most operational details. The output schema exists but is not shown; description does not explain return values, but that is acceptable per rules. The main gap is the weak parameter documentation, which slightly detracts from completeness.

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

Parameters2/5

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

The input schema has 0% description coverage, so the description must compensate. The only parameter, api_key, is described as 'The api key to analyze or process,' which is vague. Behavioral transparency mentions it for pro tiers, but the parameter description itself lacks detail on purpose, format, or impact.

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 starts with a clear, specific statement: 'Current CSRD enforcement phase-in schedule + Member State transposition status.' This distinguishes it from sibling tools like classify_entity or double_materiality_assessment, which cover different compliance aspects.

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 includes explicit 'When to use' and 'When NOT to use' sections, providing context for compliance assessment and explicitly warning against substituting legal counsel. However, it does not directly compare with sibling tools, leaving the agent to infer when to choose this one over alternatives.

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/csrd-compliance-mcp'

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