Skip to main content
Glama

search_tenders

Read-onlyIdempotent

Free during beta. Find OPEN public tenders (deadline still in the future) by keywords, country, region, CPV sector and value. EU-wide from TED; for Portugal also every national call for tender of any value (Diário da República). Returns title, buyer, country, region, CPV codes, estimated value, submission deadline, official link and tender documents link, plus 'competition': how contested this buyer's past contracts in the same kind of work were (median bidders, single-bid share, median % below the estimate, sample size). Use bid_intelligence for a price range and rivals. If nothing matches exactly, it widens (the place's whole district, then without keywords, then without the place) and says so in 'widened_to' and 'note'.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10, max 25
regionNoPlace name: district or municipality (e.g. 'Lisboa', 'Sintra'). Matches the work location or the buyer's name; most precise for Portugal.
keywordsNoWhat you are looking for. English works across all countries (matched via the EU CPV vocabulary); adding the same words in the target country's language (e.g. 'school renovation escola requalificação') also matches tender titles and descriptions.
countriesNoISO 3166-1 alpha-2 country codes where the work is performed, e.g. ["PT","ES"]
max_valueNoMaximum estimated value
min_valueNoMinimum estimated value
cpv_prefixesNoCPV code prefixes; '45' = construction, '72' = IT services, '3021' = computers
deadline_afterNoISO date; default now

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / region
      Added value: +{
      +  "description": "Place name: district or municipality (e.g. 'Lisboa', 'Sintra'). Matches the work location or the buyer's name; most precise for Portugal.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), and the description adds substantial behavior beyond them: beta pricing, source coverage per geography, the full return payload, the meaning of the 'competition' metric, and the widening fallback sequence with its 'widened_to' and 'note' signals. This is exactly the kind of behavioral context an agent cannot get from structured fields.

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?

Dense and front-loaded with purpose before the alternative and fallback details, and most sentences carry distinct information. It is on the long side, but little is redundant given the number of distinct behaviors (sources, returns, competition metric, widening) it must convey.

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?

With no output schema, the description carries the return-value burden and does so thoroughly: title, buyer, country, region, CPV codes, estimated value, deadline, official link, documents link, plus the derived 'competition' metric. Combined with the fallback behavior and sibling routing, an agent has everything needed to call and interpret it.

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; the description goes slightly beyond by explaining the widening order that relaxes the place, then keywords, then the place entirely, which clarifies how region and keywords degrade when no exact match exists. Most other param meaning (keywords language handling, region matching) is already in the schema descriptions.

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 and resource ('Find OPEN public tenders') with the exact filter dimensions (keywords, country, region, CPV sector, value) and names the data sources (TED EU-wide, Diário da República for Portugal). It also distinguishes itself from the sibling bid_intelligence by routing price/rival analysis there.

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?

Explicitly names bid_intelligence as the alternative for price ranges and rivals, which tells the agent when to prefer that sibling. It gives clear context (open tenders, deadline in the future) but does not state exclusions against other siblings such as award_history or expiring_contracts.

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