Skip to main content
Glama

eu_taxonomy_alignment_checker

Read-onlyIdempotent

[Deterministic EU Green Taxonomy alignment auditor. Pure calculation, read-only, side-effect free]. Audits economic activities by NACE Rev. 2 code against Regulation (EU) 2020/852 Technical Screening Criteria (TSC), Do No Significant Harm (DNSH) rules, and Minimum Social Safeguards (MSS), calculating aligned Turnover, CapEx, and OpEx percentages. Usage: Use this tool to verify taxonomy eligibility, taxonomy alignment, and sustainable finance disclosure metrics (SFDR Art. 8/9). Returns: JSON object with { naceCode: string, isTaxonomyEligible: boolean, technicalScreeningCriteria: object, isTaxonomyAligned: boolean, financialKpiAlignment: object, reportingStandard: string }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "naceCode": "<naceCode>"
    },
    "name": "eu_taxonomy_alignment_checker"
  }
}

Input Schema

NameRequiredDescriptionDefault
naceCodeYesNACE Rev. 2 economic activity classification code (e.g. D35.11, C23.51, F41.20)
dnshCriteriaMetNoWhether activity complies with Do No Significant Harm (DNSH) across other 5 environmental objectives
capexTurnoverEurNoFinancial KPI expenditure figures for alignment percentage calculation
activityDescriptionNoCorporate activity title
minimumSocialSafeguardsCompliantNoWhether company complies with OECD Guidelines and UN Guiding Principles
lifecycleGhgIntensityGCo2ePerKwhOrUnitNoLifecycle GHG emissions intensity for Technical Screening Criteria verification

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'pure calculation, side-effect free' and explicitly enumerates the returned JSON fields, which annotations do not cover. It does not explain how optional inputs (e.g., missing capexTurnoverEur or dnshCriteriaMet) affect the computed percentages, leaving a modest behavioral gap.

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?

Front-loads the identity and regulatory basis, then gives Usage and Returns in labeled sections, which is easy to scan. The bracketed tag preamble is somewhat stylized but short and non-redundant.

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?

For a 6-parameter tool with a nested financial object and no output schema, the description compensates by spelling out the return object shape and the regulatory framework applied. What remains thin is how the optional financial/DNSH inputs gate the alignment verdict.

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 every parameter is already documented in the schema; the description adds no per-parameter semantics. It mentions OpEx percentages that have no corresponding input in the schema, a minor mismatch rather than a contradiction.

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?

States a specific verb+resource: audits economic activities by NACE Rev. 2 code against Regulation (EU) 2020/852 TSC, DNSH, and MSS, and computes aligned Turnover/CapEx/OpEx percentages. This is clearly distinguishable from sibling tools like cbam_embedded_emissions or critical_raw_materials_screener, which cover different regulatory regimes.

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?

Provides an explicit 'Usage' line tying the tool to taxonomy eligibility, alignment, and SFDR Art. 8/9 disclosure metrics, which is clear context for selection. It stops short of naming when-not-to-use conditions or pointing to a specific alternative tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources