Skip to main content
Glama

green_claims_substantiation_audit

Read-onlyIdempotent

[Deterministic EU anti-greenwashing audit. Pure calculation, read-only, side-effect free]. Evaluates environmental claims against Directive (EU) 2024/825, auditing carbon-neutral claims for illegal offset-based compensation bans, checking generic claims against EU Ecolabel criteria, and validating PEF/LCA substantiation. Usage: Use this tool before publishing marketing claims, packaging copy, or sustainability reports in the European Union. Returns: JSON object with { isClaimLegallyPermissible: boolean, complianceStatus: string, riskLevel: string, detectedProhibitions: array, infringementCodes: array, remediationGuidance: array }.

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": {
      "claimText": "<claimText>",
      "claimType": "<claimType>",
      "substantiationMethod": "<substantiationMethod>",
      "thirdPartyCertified": "<thirdPartyCertified>"
    },
    "name": "green_claims_substantiation_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimTextYesFull environmental claim text (e.g. "100% Carbon Neutral thanks to reforestation credits")
claimTypeYesClaim classification
certifierNameNoName of accredited certification agency
claimedPercentageNoSpecific numerical percentage claimed (e.g. 40 for 40% recycled)
thirdPartyCertifiedYesWhether verified by an accredited independent body
substantiationMethodYesMethodology used to substantiate the claim
hasPublicVerificationDossierNoWhether a public summary dossier is accessible via QR code / URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description largely restates that with 'pure calculation, read-only, side-effect free' — the 'deterministic/pure calculation' framing adds some assurance value but is redundant with the structured hints. It does supply a return shape, but says nothing about input validation failures, handling of claims outside the directive's scope, or confidence/limitations of the audit.

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 bracketed tag, purpose sentence, 'Usage' and 'Returns' lines are front-loaded and scannable, with no filler prose. The only waste is the bracketed metadata duplicating the read-only annotation.

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 7-parameter, 4-required tool with no output schema, the description compensates by enumerating the returned JSON fields, so an agent knows what it will get back. The remaining gap is the absence of any statement about what happens on incomplete or non-EU inputs, which matters for an audit tool whose result is a legal verdict.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: it ties the substantiation-method enum to a legal consequence (carbon-offset-based compensation is banned) and maps generic claims to EU Ecolabel criteria, telling the agent why CARBON_OFFSETS_CREDITS or ECO_FRIENDLY_GENERIC matter. It still does not explain the roles of hasPublicVerificationDossier or certifierName in the outcome.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource — evaluates environmental claims under Directive (EU) 2024/825 — and enumerates the three sub-checks (carbon-neutral offset bans, generic claims vs. EU Ecolabel, PEF/LCA substantiation). The scope is unambiguous, but it never contrasts itself with the other EU-compliance siblings (CPR audit, CRMs screener, DPP validator), leaving that routing to inference.

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 'Usage' line gives a concrete trigger: use before publishing marketing claims, packaging copy, or sustainability reports in the EU. That is actionable context, though it states no exclusions, prerequisites, or named alternatives for cases outside the EU or for non-claim checks.

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