Skip to main content
Glama
Sign In

Greener Ahead: CSRD and VSME rules

by com.greenerahead
OverviewDiscussionsAdmin

Read an official disclosure text

explain_disclosure
Read-onlyIdempotent

Returns the official text of a disclosure in the EU voluntary standard for SMEs (VSME, B1-B11 and C1-C9) or in the ESRS (2026 edition, for example E1-8 or S1-5), with its EUR-Lex link. ESRS text is available in English, Dutch, German, French, Italian, Spanish and Polish.

Input Schema

NameRequiredDescriptionDefault
codeYesDisclosure code, for example B3 or E1-8
cursorNonextCursor from an earlier result of this tool.
sectionNoOne part of a shortened result: a "$section" path from an earlier result of this tool, for example items/0/adoption. The other arguments stay as before, and cursor pages a long part.
languageNoThe language the person writes in, for labels and headings, for example nl. Defaults to the AI app's locale, else English.
standardYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"One part of a shortened result: a \"$section\" path from an earlier result of this tool, for example items/0/adoption. Pass the other arguments as before; page a long part with cursor."New value: +"One part of a shortened result: a \"$section\" path from an earlier result of this tool, for example items/0/adoption. The other arguments stay as before, and cursor pages a long part."
  2. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "nextCursor from an earlier result of this tool.",
+  "maxLength": 8192,
+  "type": "string"
+}
    • addedInput schema / properties / section
      Added value: +{
+  "description": "One part of a shortened result: a \"$section\" path from an earlier result of this tool, for example items/0/adoption. Pass the other arguments as before; page a long part with cursor.",
+  "maxLength": 512,
+  "type": "string"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral detail - the return includes an EUR-Lex link and ESRS text exists in seven named languages (implying a language limitation on VSME). It does not disclose that results may be shortened and require the cursor/section continuation mechanism, which the schema hints at but never explains.

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?

Two dense sentences with no filler: the what and the return payload come first, then the language availability constraint. Every clause carries information the agent needs.

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?

With no output schema, the description correctly states what comes back (official text plus EUR-Lex link) and which standards/codes are valid. The only gap is the shortened-result/pagination workflow, which an agent would only discover from the schema's 'section' and 'cursor' fields.

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 80%, so the baseline is 3; the description goes further by tying 'standard' values to concrete code families (VSME B1-B11/C1-C9 vs ESRS E1-8, S1-5) and by clarifying that the language list applies to ESRS text, which the 'language' schema entry does not state. It adds no interpretation of 'section' or 'cursor', which remain purely schema-documented.

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?

States a specific verb ('Returns the official text') and a precise resource (a disclosure in VSME B1-B11/C1-C9 or ESRS, e.g. E1-8), including the EUR-Lex link. The purpose is unambiguous and clearly distinct in kind from the sibling check_reporting_obligation, though the description never names that sibling to route the agent explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use/when-not guidance and no mention of the alternative tool. The reader must infer that this is for retrieving source text rather than for determining whether a disclosure is required; nothing states prerequisites or selection criteria.

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

All Greener Ahead: CSRD and VSME rules toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources