Skip to main content
Glama

Eu Funding Tenders

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Eu Search Calls

eu_search_calls
Read-onlyIdempotent

Search Horizon Europe and every other EU funding call (grant topics) on the EU Funding & Tenders Portal by keyword. Returns the topic identifier to quote in an application (e.g. HORIZON-CL5-2026-09-D4-03), title, parent call identifier, submission deadline, status word (Open, Forthcoming, Closed), type of action, framework programme and portal URL. Answers "is there EU funding for hydrogen storage", "which Horizon Europe calls cover AI in health", "what LIFE or Erasmus+ or Digital Europe calls mention circular economy".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number (default 1).
limitNoResults per page, 1-50 (default 10).
queryNoFree-text search over topic titles, descriptions and keywords, e.g. "battery recycling". Omit to list everything matching the filters.
statusNoCall status in plain words (default "open").
programmeNoFramework programme code, e.g. "horizon", "life", "erasmus", "digital", "eu4h". Supported: horizon, h2020, life, erasmus, crea, digital, cef, eu4h, cerv, amif, isf, smp, edf, rfcs, imcap, innovfund, emfaf, ucpm, i3, pppa, euba. A raw numeric frameworkProgramme id also works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 5,
-    "query": "hydrogen storage",
-    "status": "open"
-  }
-]New value: +[
+  {
+    "limit": 10,
+    "query": "battery recycling",
+    "status": "open"
+  },
+  {
+    "limit": 10,
+    "programme": "horizon",
+    "query": "energy",
+    "status": "open"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and open-world hints. Description adds value by listing return fields (topic identifier, title, deadline, status, type, programme, URL) and mentioning it searches the EU Funding & Tenders Portal. No contradictions.

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

Conciseness5/5

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

Two sentences: first states core purpose, second lists return fields and gives example queries. Every sentence serves a purpose; no fluff. Front-loaded with essential action.

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 5 parameters and no output schema, description covers return fields adequately. Combined with schema, the tool is well-documented. Could mention pagination or rate limits, but not critical for a search tool.

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 baseline is 3. Description adds meaning by providing example values for query and status, explaining query as optional ('Omit to list everything'), and listing supported programmes. This extra context justifies a 4.

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?

Description clearly states the verb 'search' and resource 'EU funding calls', specifies scope (Horizon Europe and other frameworks), and provides examples. It distinguishes from siblings like eu_open_calls and eu_get_topic by emphasizing keyword search across multiple programmes.

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?

Description explains what the tool does and gives example questions it answers, implying when to use it (keyword search across calls). However, it does not explicitly state when not to use it or mention alternatives like eu_open_calls for only open calls, but sibling context helps.

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

All Eu Funding Tenders toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources