Skip to main content
Glama

AY Tenders

Search open tenders

search_open_tenders
Read-onlyIdempotent

Open calls for bids in our seven sectors, nearest deadline first. Needs at least one of query, sector, country or closes_within_days: there is no list of everything. Up to 10 rows an answer and 3 pages; 300 rows a day per address. Each row has the official notice (official_url) and our page (page_url) when we have one.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
queryNoWords in the title or the buyer's name, in the notice's language.
regionNouk, us, or eu (every other country).
sectorNoit_services = IT systems & software, cybersecurity = Cybersecurity, medical_devices = Medical devices & pharmaceuticals, civil_works = Civil works & construction, energy_solar = Energy, solar & efficiency, cleaning_environment = Cleaning, environment & waste, events_marketing = Events, exhibitions & marketing.
countryNoThe buyer's country, two letters (GB, DE, US...).
closes_within_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses the practical behavior an agent cannot infer: a 10-row page cap, a 3-page depth limit, and a 300-rows-per-day budget per address. It also describes what a row contains (official_url, page_url), which matters for downstream use.

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 sentences, front-loaded with purpose, then the required-filter rule, then the operational caps. No filler and no repetition of enum values already in the schema.

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 compensates by describing the row payload and the two URL fields an agent will need. Combined with paging, rate limits and the at-least-one-filter rule, an agent has everything needed to call this correctly and interpret results.

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 67%, and the description adds the one constraint the schema cannot express: that the four filter parameters are collectively at-least-one required. It also ties sector scope to "seven sectors" and the result ordering to deadlines. The region parameter is never referenced in the description, leaving that one gap.

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?

"Open calls for bids in our seven sectors, nearest deadline first" gives a specific resource, a domain scope, and the result ordering, which is enough to separate it from single-item lookups like get_tender. It does not explicitly contrast with expiring_contracts, so sibling differentiation is implied rather than stated.

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?

The description states a hard precondition — at least one of query, sector, country or closes_within_days — and warns "there is no list of everything," which is exactly the guidance an agent needs to avoid an empty call. It stops short of naming alternatives to use instead when no filter applies, so no exclusions are made explicit.

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