CSRD Compliance MCP

Overview Schema Source Related Servers Discussions Admin

ghg_emissions_readiness

Assess compliance readiness for ESRS E1 climate emissions by analyzing Scope 1, 2, and 3 tracking against GHG Protocol methodology. Identify gaps and generate compliance documentation.

Instructions

Check ESRS E1 (Climate) Scope 1/2/3 emissions readiness. scopes_tracked: comma-separated list (e.g. 'scope 1, scope 2 location-based, scope 2 market-based'). methodology: e.g. 'GHG Protocol'.

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: scopes_tracked (str): The scopes tracked to analyze or process. methodology (str): The methodology to analyze or process. 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ghg_emissions_readiness"
  }
}

Input Schema

Name	Required	Description	Default
`scopes_tracked`	No
`methodology`	No
`api_key`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4May 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description fully covers side effects (read-only, stateless), authentication (none for basic, API key for pro), rate limits (free 10/day, pro unlimited), error handling (structured error objects), idempotency, and data privacy. This is comprehensive and exceeds expectations.

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-structured with clear sections and front-loads the core purpose. It is slightly verbose but every section adds value. Could be tightened while retaining information.

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 tool has 3 parameters with no required fields, and the description includes detailed behavioral transparency, usage guidelines, and parameter context, it is complete and addresses all key aspects for an agent to use the 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 description provides examples for scopes_tracked and methodology (e.g., 'scope 1, scope 2 location-based', 'GHG Protocol'), adding meaning beyond the schema. The api_key parameter is mentioned but lacks detailed semantics, though authentication context compensates. Given 0% schema coverage, this is strong.

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 checks ESRS E1 (Climate) Scope 1/2/3 emissions readiness. It uses a specific verb ('check') and resource, and effectively distinguishes from siblings like double_materiality_assessment by focusing on readiness assessment.

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 clear context for assessment, audit, and verification purposes. It warns against substituting for legal counsel but does not reference specific sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server