Skip to main content
Glama

search_tenders

Search live open EU public tenders by keywords, CPV code, country, and publication window; get future-deadline tender cards with buyer, budget, deadline, and link.

Instructions

Search open EU public tenders (TED, live). Returns cards: id, title, buyer, country, budget, currency, deadline, url. Only tenders with a future deadline are returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesFree-text keywords, e.g. "software development". May be empty.
cpvNoCPV code prefixes, e.g. ["72"] for IT services.
daysNoLook at notices published in the last N days (default 30).
limitNoMax cards to return (default 10, max 20).
countriesNoISO 3166-1 alpha-2 buyer countries (EU/EEA), e.g. ["DE","FR"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 usefully discloses two non-obvious behaviors — results are live TED data and only tenders with a future deadline are returned — plus the exact card fields. It omits auth requirements, rate limits, result ordering, and what an empty result looks like.

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?

Three short sentences, front-loaded with the core purpose and followed by the return shape and the key filter constraint. Nothing is wasted or repeated from structured fields.

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 read-only search tool with no output schema, the description compensates well by enumerating the returned card fields and the deadline filter. Missing pagination/ordering and failure-mode detail are the only notable gaps.

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%, so the baseline is 3, but the description adds a real semantic distinction: the future-deadline constraint is separate from the `days` publication window, clarifying how filtering actually works. It still does not explain how `q` combines with `cpv` or how matching/ranking behaves.

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 names a specific verb (Search), a precise resource (open EU public tenders), the data source and freshness (TED, live), and even states the return unit (cards). An agent knows exactly what domain and data it gets back without opening the schema.

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?

The phrase 'open EU public tenders (TED, live)' implies the appropriate context, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. With no siblings listed, the omission is defensible, but the description still leaves the agent to infer the trigger conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools