Skip to main content
Glama

de_minimis_state_aid_screener

Read-onlyIdempotent

[EU De Minimis State Aid auditor. Pure calculation, read-only, side-effect free]. Audits state aid applications against the new €300,000 3-year rolling ceiling under Commission Regulation (EU) 2023/2831, consolidating linked enterprises under the single undertaking ('Impresa Unica') rule and sector restrictions. Usage: Use this tool to verify available de minimis subsidy headroom before submitting public grant applications. Returns: JSON object with { companyName: string, isEligibleForRequestedAid: boolean, statutoryCeilingEur: number, totalPriorAidAccumulatedEur: number, remainingHeadroomAvailableEur: number, singleUndertakingAudit: object, complianceVerdict: 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": {
      "companyName": "<companyName>",
      "companyVatOrId": "<companyVatOrId>",
      "economicSector": "<economicSector>",
      "requestedAidAmountEur": "<requestedAidAmountEur>",
      "requestDateIso": "<requestDateIso>",
      "priorAidsGrantedIn3YearRollingWindow": "<priorAidsGrantedIn3YearRollingWindow>"
    },
    "name": "de_minimis_state_aid_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNameYesApplicant legal enterprise name
companyVatOrIdYesEnterprise tax ID or national VAT number
economicSectorYesEconomic activity sector for ceiling determination
requestDateIsoYesDate of aid application (YYYY-MM-DD)
requestedAidAmountEurYesGross grant equivalent of requested state aid in EUR
linkedEnterprisesPriorAidTotalEurNoTotal de minimis aid granted to linked enterprises in the single undertaking
priorAidsGrantedIn3YearRollingWindowYesList of prior de minimis subsidies conceded across 3-year rolling window
hasLinkedEnterprisesInSingleUndertakingNoTrue if applicant is part of a corporate group under Art. 2(2) single undertaking rule

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, read-only, side-effect free', so it is consistent but partly redundant. It does add genuine behavioral context the annotations cannot: the applicable legal regime, the Impresa Unica consolidation logic, and treatment of sector restrictions.

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 structure is front-loaded and scannable: bracketed scope marker, Usage line, Returns line. The 'pure calculation, read-only, side-effect free' clause largely duplicates the annotations and is the one piece of text that does not fully earn its place.

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?

With no output schema, the description compensates by enumerating the returned JSON fields, including complianceVerdict and remainingHeadroomAvailableEur. Combined with 100% parameter coverage and 8 parameters, an agent has everything needed to call and interpret it.

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 earns a bump by explaining why inputs matter: the 3-year rolling window, the single-undertaking aggregation behind linkedEnterprisesPriorAidTotalEur, and sector-based ceiling determination for economicSector. It adds regulatory meaning rather than restating field names.

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 states a specific verb and resource ('Audits state aid applications against the new €300,000 3-year rolling ceiling under Commission Regulation (EU) 2023/2831'), including the consolidation rule and sector restrictions. It is clearly distinguishable from a GBER-intensity checker by implication, but it never names a sibling or explicitly contrasts its scope with the alternatives, so it stops short of a 5.

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?

'Use this tool to verify available de minimis subsidy headroom before submitting public grant applications' gives a concrete triggering situation. There is no when-not guidance and no routing to alternatives such as the GBER aid intensity checker, which is the main gap.

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