Skip to main content
Glama

Search active EU public tenders on TED

eu_tenders
Read-only

Active EU public tenders from TED matching words, optionally for one buyer country: notice number, title, buyer, country, publication date, deadline, CPV codes and link, newest first. Country is an ISO alpha-3 code (DEU, FRA, POL). Attribution: TED, EU open data. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
qNoKeywords
countryNoISO 3166 alpha-3 buyer country, e.g. DEU

Output Schema

NameRequiredDescriptionDefault
queryNo
totalNo
sourceNo
tendersNo
checkedAtNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses result ordering ('newest first'), the exact fields returned, the data source and attribution requirement, and a concrete payment model ($0.002 per successful call via x402 USDC, failed calls free). The billing/auth detail is exactly the kind of context annotations cannot convey and would otherwise cause failed calls.

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?

Core purpose and output shape are front-loaded in the first sentence, with country format, attribution, and pricing following in descending priority. The sentences are dense but each carries information an agent needs; nothing is filler.

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?

For a simple two-optional-parameter search with an output schema, the description covers purpose, result shape, ordering, country format, attribution, and cost. Return values are also backed by an output schema, so nothing an agent needs to invoke this correctly is missing.

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 both parameters are already documented with types and an example. The description's 'ISO alpha-3 code (DEU, FRA, POL)' restates the schema example rather than adding new meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource ('Active EU public tenders from TED') and the matching behavior (keywords, optional buyer country), and enumerates the returned fields, so an agent knows exactly what comes back. It does not differentiate against siblings, but the sibling list contains no comparable tender-search tool, so the missing comparison is low-cost.

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?

'Active' scopes the tool to currently open tenders, and 'optionally for one buyer country' makes clear the country filter is not required, which is the main usage decision for a two-parameter search. There are no explicit when-not conditions or named alternatives, but none exist in this catalog.

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