Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_eu_horizon_grants

Read-onlyIdempotent

Search open and forthcoming EU grants and tenders across Horizon Europe, Digital Europe, EIC, LIFE, and EDF; filter by keyword, budget, or deadline and return parsed EUR amounts and submission dates.

Instructions

Search open and forthcoming European Commission grants and tenders (Horizon Europe, Digital Europe, EIC, LIFE, EDF) via SEDIA API with parsed EUR topic budgets and submission deadlines (corridordata/eu-horizon-grants-funding-calls).

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

Input Schema

NameRequiredDescriptionDefault
maxItemsNoMaximum EU funding calls or tenders to return.
statusesNoCall statuses to include.
minBudgetEurNoMinimum parsed topic budget in EUR.
searchKeywordNoTechnology or topic keyword (e.g. 'AI', 'quantum', 'cybersecurity', 'hydrogen').
opportunityTypesNoInclude EU Grants, EU Tenders, or both.
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the description only needs to add context. It contributes the upstream data source, the fact that budgets and deadlines are parsed, and the backing dataset slug, but says nothing about result shape, pagination, or refresh latency.

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?

A single front-loaded sentence with no filler; the parenthetical programme list and dataset slug are dense but each carries identifying information. Slightly over-packed into one sentence, which costs a little readability.

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 all parameters documented in the schema, annotations covering safety, and no output schema to explain, the description supplies the essential scope, source and data-quality context. Missing only minor operational detail such as default result limits and status defaults, which the schema already covers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every one of the six parameters is already documented in the schema. The description only loosely echoes budget and deadline handling and adds no filtering semantics (e.g. how keyword matching works against topics) beyond the schema.

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 ('Search open and forthcoming European Commission grants and tenders'), enumerates the covered programmes (Horizon Europe, Digital Europe, EIC, LIFE, EDF) and names the upstream source (SEDIA API), which clearly separates it from the Spain/UK/global tender siblings.

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

Usage Guidelines3/5

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

The EU/EC scoping and the 'open and forthcoming' framing imply when this tool applies, but there is no explicit when-to-use/when-not statement and no routing to alternatives such as search_global_tenders or search_spain_public_tenders for non-EU coverage. Usage is inferable rather than stated.

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