Skip to main content
Glama

EU Tender Radar (TED)

search_eu_open_tenders

Open EU public tenders (TED contract notices whose deadline has not passed), newest first. Filters: EU/EEA countries (ISO alpha-3), CPV prefix, keyword, days back. Source: TED (c) European Union, reused under Commission Decision 2011/833/EU. Not affiliated with the EU.

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_open_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvNo
daysNo
limitNo
keywordNo
countriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two real behavioral traits beyond structured data — results are restricted to notices whose deadline has not passed, and ordering is newest first — plus the TED data source. However, it says nothing about return fields, pagination/limit behavior, auth, or rate limits, which are notable gaps for an unannotated tool with no output schema.

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 resource definition, followed by a compact filter list — very little waste. The trademark/licensing sentence is boilerplate but plausibly required attribution for TED data, so it earns a modest place.

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?

For a five-optional-parameter read-only search with no output schema, the definition covers the essential scoping (open notices only, ordering, filter semantics, source). What is missing is minor but real: the 'limit' parameter, what a returned notice contains, and any steering toward the sibling awards tool.

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 coverage is 0%, so the description must compensate, and it partially does: it explains that 'countries' takes ISO alpha-3 codes, that 'cpv' is a prefix match, that 'keyword' is a free-text search, and that 'days' means days back. The fifth parameter, 'limit', is never mentioned, and no format examples or interaction notes (e.g., how CPV prefix narrows results) are given.

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?

States a specific verb-object with scope: 'Open EU public tenders (TED contract notices whose deadline has not passed), newest first.' The parenthetical definition of 'open' and the source attribution make the resource unambiguous, and 'open' vs. the sibling's awards focus gives implicit differentiation. It stops short of explicitly naming the alternative, which keeps it from a 5.

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?

Usage is only implied: an agent can infer this is for finding currently-open opportunities and that filtering is done via the listed facets. There is no when-to-use/when-not guidance, no mention of when to prefer the single-bidder-awards sibling, and no note that all filters are optional and combinable.

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