Skip to main content
Glama

gber_aid_intensity_checker

Read-onlyIdempotent

[GBER Article 25 R&D&I aid intensity & subsidy ceiling auditor. Pure calculation, read-only, side-effect free]. Audits maximum allowable public aid intensities for R&D projects under General Block Exemption Regulation (EU) No 651/2014, computing base rates (Fundamental 100%, Industrial 50%, Experimental 25%), SME top-ups (+10%/+20%), and collaboration bonuses (+15%) up to the statutory 80% cap. Usage: Use this tool to verify that public research co-funding complies with EU State Aid notification exemptions. Returns: JSON object with { projectTitle: string, researchCategory: string, baseAidIntensityPercent: number, smeTopUpPercent: number, collaborationBonusPercent: number, finalAllowableAidIntensityPercent: number, statutoryMaxCapEnforced: boolean, financialCalculations: object }.

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": {
      "projectTitle": "<projectTitle>",
      "enterpriseSize": "<enterpriseSize>",
      "researchCategory": "<researchCategory>",
      "eligibleCostsEur": "<eligibleCostsEur>"
    },
    "name": "gber_aid_intensity_checker"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectTitleYesR&D project title
enterpriseSizeYesEnterprise size according to EU Recommendation 2003/361/EC
eligibleCostsEurYesTotal eligible project research expenditure in EUR
researchCategoryYesCategory of research activity ex Art. 25 GBER
hasWideDisseminationOpenAccessNoTrue if research results will be widely disseminated through open access or free software
hasEffectiveCrossBorderCollaborationNoTrue if project involves cross-border collaboration between independent enterprises
hasCollaborationWithResearchOrganizationNoTrue if project involves collaboration with a university or research organization bearing at least 10% of costs

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?

The annotations already declare readOnlyHint=true and idempotentHint=true, so 'pure calculation, read-only, side-effect free' largely repeats structured data. What does add value beyond annotations is the disclosure of the actual computation rules (100%/50%/25% base rates, +10%/+20% SME top-ups, +15% collaboration bonus) and the fact that a statutory 80% cap is enforced and reported back via a flag. It stops short of stating validation or failure behavior.

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 strong and front-loaded: bracketed safety note, then purpose and calculation rules, then usage, then return shape. It is dense but nearly every clause carries information; the 'read-only, side-effect free' clause is the one piece that duplicates the annotations rather than adding to them.

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 explicit Returns enumeration (field names including statutoryMaxCapEnforced and financialCalculations) is essential and present. Remaining gaps are minor: the feasibility-study rate and the small-vs-medium top-up split are unspecified, and no note explains what happens with ineligible or missing bonus combinations.

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 description coverage is 100%, so the baseline is 3, but the description earns more by mapping enum values to concrete rate outcomes (Fundamental 100%, Industrial 50%, Experimental 25%) and by identifying the collaboration and dissemination parameters as bonus drivers. The mapping is incomplete: no rate is given for FEASIBILITY_STUDY, and the +10% vs +20% split between small and medium enterprises is not tied to specific enum values.

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 domain artifact and operation: an 'R&D&I aid intensity & subsidy ceiling auditor' that computes base rates, SME top-ups, collaboration bonuses and enforces the 80% statutory cap. That scope is specific enough to implicitly separate it from a de minimis aid screener or other compliance checkers, but it never explicitly contrasts itself with a named sibling, so it lands at 4 rather than 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 that public research co-funding complies with EU State Aid notification exemptions' gives a clear triggering context. There are no exclusions, though – nothing tells the agent when this tool is the wrong instrument (e.g. de minimis schemes or non-Art. 25 aid) or which sibling handles those cases.

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