Skip to main content
Glama

Bindler: UAE Corporate Tax, CSRD scope, EU AI Act, CBAM and statutory deadlines

csrd_scope

Read-onlyIdempotent

Returns the CSRD verdict per financial year under Directive (EU) 2022/2464 as amended by the Stop-the-clock Directive (EU) 2025/794 and Omnibus I Directive (EU) 2026/470, with the size test and the third-country test shown separately. Use it when someone asks: does CSRD apply to my company, do we have to report under CSRD, are we in scope after the Omnibus, did the postponement take us out of scope, when is our first CSRD report due, which reporting wave are we in, do the 1,000 employee and turnover thresholds catch us, are we a large undertaking, does CSRD apply to a non-EU or US parent with EU subsidiaries, which ESRS standard applies to us, do we need limited or reasonable assurance, do we have to report for financial year 2026 or 2027.

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": "csrd_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
employeesNoAverage employees during the financial year.
net_turnover_eurNoNet turnover in EUR.
established_in_euNoIs the undertaking established in the EU? Default true. Set false to run the third-country test instead.
group_eu_turnover_eurNoThird-country test only: group turnover generated in the EU, current year.
balance_sheet_total_eurNoBalance sheet total in EUR.
eu_subsidiary_turnover_eurNoThird-country test only: turnover of the EU subsidiary or branch.
group_eu_turnover_prior_year_eurNoThird-country test only: the same figure for the prior year.
member_state_used_the_postponement_optionNoHas the Member State used the Omnibus I option for financial years beginning 1 Jan 2025 to 31 Dec 2026? Default false.
securities_listed_on_an_eu_regulated_marketNoListed on an EU regulated market. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds that the size test and third-country test are reported separately per financial year, which is genuine output-shape information beyond the annotations, but it never states what a verdict looks like (in-scope/out-of-scope values) or how missing inputs are handled when all parameters are optional.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is well front-loaded and carries the legal citations, but the following catalogue of user questions is bloated and repetitive — 'does CSRD apply to my company' and 'do we have to report under CSRD' say the same thing, and several questions (ESRS standard, assurance level) go beyond a scope verdict. A trimmed list would lose nothing.

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 nine-parameter, all-optional classifier with no output schema, the description does the needed work: it names the two tests, the legal basis, and the classes of questions answered. The remaining gap is that with no output schema the description should say what the verdict field(s) contain, which it only gestures at.

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; however the description adds real semantic framing by explaining that the size test and the third-country test are evaluated separately, and by listing the employee/turnover threshold question, which is what the employee and turnover parameters feed. It does not explain the interplay of the postponement-option flag or how partial inputs degrade the verdict, so it is not a 5.

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 and resource — returns the CSRD verdict per financial year — and anchors it to the exact legal instruments (2022/2464 as amended by 2025/794 and 2026/470). It is unmistakably distinct from the sibling tools (cbam_cost, eu_ai_act_classify, uae_corporate_tax), which address different 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 unusually rich set of trigger phrasings, including the ambiguity cases that matter (post-Omnibus scope, postponement opt-out, first reporting year, third-country parent with EU subsidiaries). It stops short of naming when NOT to use it or pointing to a sibling for adjacent questions such as deadlines, which keeps it from a 5.

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