Skip to main content
Glama

Eu Funding Tenders

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Eu Open Calls

eu_open_calls
Read-onlyIdempotent

Currently open EU funding calls ordered by nearest submission deadline first, with days remaining computed at request time. Answers "what EU grants can I still apply for", "which Horizon Europe calls close soon", "what is the next EU funding deadline for renewable energy". Each row carries the topic identifier, title, deadline date, days until deadline, type of action, framework programme and portal URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many calls to return, 1-50 (default 10).
queryNoOptional free-text filter, e.g. "quantum" or "SME innovation".
programmeNoOptional framework programme code, e.g. "horizon", "life", "cef". Supported: horizon, h2020, life, erasmus, crea, digital, cef, eu4h, cerv, amif, isf, smp, edf, rfcs, imcap, innovfund, emfaf, ucpm, i3, pppa, euba.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 5,
-    "programme": "horizon"
-  }
-]New value: +[
+  {
+    "limit": 10,
+    "programme": "horizon",
+    "query": "quantum"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive. The description adds value by disclosing that days remaining are computed at request time, ordering by deadline, and listing output fields. No contradictions with annotations.

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?

The description is four sentences, each adding unique value: core purpose, example queries, output fields. No fluff or redundancy. Front-loaded with the main functionality.

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?

Given no output schema, the description adequately describes return format (topic identifier, title, deadline, days remaining, type, programme, URL). Covers purpose, sorting, and parameter implications. With 100% schema coverage and clear output description, it is complete.

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% and parameters are well-documented. The description adds ordering behavior (by nearest deadline) and computed days, which is not in the schema. This provides useful semantic context beyond the parameter descriptions.

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?

The description clearly states the tool lists currently open EU funding calls sorted by nearest submission deadline, with computed days remaining. It answers specific user queries like 'what EU grants can I still apply for,' distinguishing it from siblings like eu_search_calls (which likely searches across all calls) and eu_get_topic (which retrieves a specific topic).

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 description implicitly guides when to use this tool: for open calls ordered by deadline. However, it does not explicitly exclude alternative tools or provide when-not-to-use guidance. Sibling names (eu_search_calls, eu_get_topic) suggest differentiation, but the description could be more explicit about scope.

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