Skip to main content
Glama

EU Tender Radar (TED)

search_eu_single_bidder_awards

EU contracts awarded after only ONE tender was received (single-lot TED contract award notices), newest first, with the winning company and value. Looks at the newest 100 matching award notices only. 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_single_bidder_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvNo
daysNo
limitNo
keywordNo
countriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key behavior: results are newest-first, capped at the newest 100 matching notices, and include the winning company and value. It omits freshness/latency, rate limits, and what happens when a filter matches nothing, but the hard result cap is the most important trait and it is stated plainly.

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?

The behavioral core is front-loaded in the first sentence and the cap is stated immediately after. The source/licensing attribution is defensible for a TED-derived dataset, though the trailing 'Not affiliated with the EU' line is boilerplate that adds little for tool selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter tool with no annotations and no output schema, the description covers purpose, ordering, result content, and the 100-notice ceiling. It is still incomplete on the parameter surface, which is entirely undocumented, and does not explain how 'limit' and the 100-notice cap combine.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description says nothing about any of the five parameters. It never explains what 'cpv' means, that 'days' is a lookback window, how 'countries' interacts with 'keyword', or how the 'limit' (max 25) relates to the 100-notice cap, so an agent must guess from terse names and regex patterns.

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 names a precise resource: EU contract award notices where only one tender was received, including the winner and value. That is far more specific than the tool name alone and implicitly separates it from open-tender search, but it never explicitly contrasts with the sibling search_eu_open_tenders.

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 researching single-bidder awards. There is no explicit statement of when to choose this over the open-tenders sibling, no prerequisites, and no guidance on what to do when the 100-notice cap is insufficient.

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