Skip to main content
Glama

horizon_europe_budget_calculator

Read-onlyIdempotent

[Horizon Europe project budget & EU grant calculator. Deterministic calculation, read-only, side-effect free]. Calculates eligible direct personnel, subcontracting, and other direct costs, applying the mandatory 25% flat-rate indirect cost overhead and statutory reimbursement rates (100% RIA/CSA, 70% IA for profit entities) under the Horizon Europe Model Grant Agreement. Usage: Use this tool to construct, normalize, and audit consortium budget proposals for European research grants. Returns: JSON object with { projectAcronym: string, actionType: string, reimbursementRatePercent: number, budgetBreakdown: object, statutoryRulesApplied: 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": {
      "projectAcronym": "<projectAcronym>",
      "actionType": "<actionType>",
      "beneficiaryType": "<beneficiaryType>",
      "projectDurationMonths": "<projectDurationMonths>",
      "workPackages": "<workPackages>"
    },
    "name": "horizon_europe_budget_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionTypeYesHorizon Europe funding action type
workPackagesYesArray of Work Package expenditure allocations
projectAcronymYesHorizon Europe proposal project acronym
beneficiaryTypeYesLegal entity classification of participant
projectDurationMonthsYesGrant implementation duration in months

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 'deterministic calculation, read-only, side-effect free'. Beyond that it discloses real domain behavior the annotations do not: the mandatory 25% flat-rate indirect overhead and the statutory reimbursement rates (100% RIA/CSA, 70% IA for profit entities). It stops short of stating rounding/currency conventions or validation failures, which keeps it from a 5.

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?

Front-loaded with a bracketed scope/behavior tag, then calculation rules, then usage, then return shape. Dense and mostly waste-free, though the explicit 'Returns:' field list partially duplicates what the schema contract implies and could be trimmed.

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?

No output schema exists, but the description supplies the return shape ({ projectAcronym, actionType, reimbursementRatePercent, budgetBreakdown, statutoryRulesApplied }), and all five required inputs are fully documented in the schema. Edge behavior such as invalid durations or zero-cost work packages is not covered, a minor gap for a calculator of this complexity.

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 schema documents each parameter and the baseline is 3. The description adds meaning the schema does not carry: it ties actionType to concrete reimbursement percentages and explains that subcontracting is exempt from the 25% overhead. That mapping gives the enum values operational significance.

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?

Names a specific verb and resource ('Calculates eligible direct personnel, subcontracting, and other direct costs') and pins the domain precisely: Horizon Europe budget under the Model Grant Agreement. The scope (personnel + subcontracting + other direct + 25% flat-rate indirect) makes it unmistakable against sibling calculators like bando_thresholds_calculator or de_minimis_state_aid_screener.

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 clear context: construct, normalize, and audit consortium budget proposals for European research grants. It states when to reach for it but offers no exclusions or explicit alternative-routing, so an agent knows the situation but gets no negative guidance.

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