Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Search public tenders and contract awards

search_tenders
Read-onlyIdempotent

Find open public procurement notices from official portals worldwide by keywords, codes, sectors, countries, deadlines, and value; filter awards or tenders and return normalized results.

Instructions

Public procurement notices from official portals in one schema: US SAM.gov (federal), EU TED (every EU/EEA country), UK Find a Tender and Contracts Finder, France BOAMP, Spain PLACSP, Germany, Netherlands TenderNed, Canada CanadaBuys, Colombia SECOP II, Brazil PNCP, India GeM, Ukraine Prozorro, EU institutions (Funding & Tenders portal), US contract awards (USAspending), Australia AusTender (awards) and South Africa eTenders. Title, buyer, deadline, value and currency, CPV/UNSPSC/NAICS codes, sectors, buyer contacts, suppliers for awards, notice link. Open tenders by default. Runs the Apify Actor tacps126/tenders-radar on your Apify account (about $0.004 per notice; spend per call is capped at $0.5).

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
codesNoCPV, UNSPSC, NAICS or PSC code prefixes, e.g. ["72"] for IT services (CPV) or ["5415"] (US NAICS).
statesNoStates or regions by name or ISO 3166-2 code, e.g. ["Texas", "IN-MH"]; where the work is or the buyer sits.
sectorsNoSectors from CPV/UNSPSC/NAICS/PSC codes and multilingual terms (housing = construction and real estate).
keywordsNoWords matched literally on title and description; add translations for non-English portals, e.g. ["software", "logiciel"].
countriesNoISO codes, e.g. ["US", "GB", "FR", "CA"], or "EU" for every EU/EEA country.
max_itemsNoMaximum results to return (default 30, max 500). Cost scales with this.
min_valueNoMinimum estimated value in the notice currency.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
notice_typesNotender = open opportunities; award = who won and for how much.
posted_within_daysNoOnly notices from the last N days.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.12.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the underlying Apify Actor, per-notice cost, and a per-call spend cap of $0.5. It also states the default notice type and enumerates covered portals and fields, which are critical operational details for an open-world search tool.

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 description is dense but front-loads the core purpose, coverage, and returned data before cost details. The long portal list is somewhat expansive, but it earns its place by clarifying geographic and source coverage for a broad procurement search.

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?

Given the complex multi-source nature of the tool, the description supplies the key missing context: portal coverage, returned fields, default notice type, cost model, and spend cap. With annotations and a full output schema present, no essential invocation context is missing.

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 description coverage is 100%, so every parameter is already well documented in the input schema. The description reinforces the default of open tenders and mentions returned fields, but it does not add substantial parameter-level meaning beyond the schema.

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 the specific resource (public procurement notices/tenders and awards), lists the exact official portals covered, and states the returned fields and default behavior. An agent can immediately distinguish this from generic grant, news, or supplier-contract siblings.

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?

It clearly frames the use case as official public procurement notices and explicitly notes that open tenders are returned by default, with awards available via notice_types. It does not explicitly compare against sibling tools such as search_grants or get_supplier_contracts, but the domain context is strong enough to select it confidently.

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