Skip to main content
Glama

Eu External Action Tenders

eu_external_action_tenders
Read-onlyIdempotent

Search EuropeAid external-action contracts, the European Commission's own development cooperation, humanitarian aid and technical assistance tenders, published on the EU Funding & Tenders Portal with EuropeAid/... references. Covers roughly 2,400 records, all Commission-funded work delivered in partner countries. Returns the reference, title, contract budget and currency, submission deadline, status word, geographical zone and portal URL. Answers "what EuropeAid contracts are open in Nigeria", "which EU development contracts cover water infrastructure", "EU technical assistance tenders in the Sahel". For a contract notice published by a national or municipal buyer inside the EU, that is TED (Tenders Electronic Daily), a separate and far larger journal.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 10,
      "query": "water",
      "status": "any"
    },
    "name": "eu_external_action_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number (default 1).
limitNoResults per page, 1-50 (default 10).
queryNoFree-text search over tender titles and descriptions, e.g. "cloud services" or "Kenya energy".
statusNoTender status in plain words (default "open").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the description's job is to add domain context — and it does: corpus size, that all records are Commission-funded partner-country work, and the specific fields returned. It says nothing about pagination limits beyond the schema or about freshness/latency of the underlying journal, which is the main remaining gap.

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 the verb and resource, then scope, then return fields, then example queries, then the sibling-journal exclusion — a logical order with no filler sentences. It is on the long side, and the three example questions plus the enumerated return fields make it denser than strictly necessary, but each element carries information.

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?

There is no output schema, so the description carries the burden of explaining returns, and it does so thoroughly (reference, title, budget, currency, deadline, status, geographical zone, portal URL). Combined with the corpus size and coverage statements, an agent has enough to call this correctly and interpret results; only result ordering and pagination behavior are left implicit.

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%, with each parameter documented in the schema including the status enum and default, so the baseline of 3 applies. The description mentions 'status word' and 'contract budget and currency' in the return-field list, which lightly reinforces parameter meaning, but it adds no syntax or query-construction guidance beyond what the schema already says.

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 (search), a precisely bounded resource (EuropeAid external-action contracts on the EU Funding & Tenders Portal with EuropeAid/... references), and quantifies scope (~2,400 records, Commission-funded work in partner countries). It also names the boundary case it is not — TED — so an agent can distinguish it without opening any schema.

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?

Gives concrete use contexts through three representative questions (open contracts in Nigeria, water infrastructure coverage, technical assistance in the Sahel) and an explicit exclusion rule: national or municipal buyers inside the EU belong to TED instead. What it does not do is guide selection among the EU-focused siblings such as eu_open_calls or eu_search_calls, so the routing guidance is strong but not complete.

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.