Skip to main content
Glama

Worldbank Procurement

Wb Procurement Search

wb_procurement_search
Read-onlyIdempotent

Search World Bank procurement notices, tenders, invitations for bids, requests for expression of interest, contract awards, and general procurement notices for World Bank-financed international development projects in ~140 developing countries (Africa, Asia, Latin America, Middle East, Eastern Europe). ~412k notices, newest first. Full-text search plus filters: country, notice type, and procurement method (Request for Bids, Request for Proposals, consultant selection). Each result includes bid reference, project, deadline, and a public notice URL. Keyless, global multilateral source.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 10,
      "query": "solar panels",
      "country": "Kenya",
      "notice_type": "Invitation for Bids"
    },
    "name": "wb_procurement_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of notices to return (1-50). Default 10.
queryNoFull-text search over notices, e.g. "solar panels", "road construction", "water supply consultant". Omit to list the latest notices.
methodNoProcurement method filter, code or name: RFB (Request for Bids), RFP (Request for Proposals), RFQ (Request for Quotations), INDV (Individual Consultant Selection), QCBS (Quality and Cost-Based Selection), LCS (Least Cost Selection), CQS (Consultant Qualification Selection), DIR (Direct Selection).
offsetNoResult offset for pagination. Default 0.
countryNoCountry filter, plain English name, e.g. "Kenya", "Somalia", "Bangladesh", "Brazil". Regional multi-country programs (e.g. "Eastern and Southern Africa") also match. Omit for worldwide.
notice_typeNoNotice type filter. Accepts the label or a shorthand: "Invitation for Bids" (bids/ifb/tender), "Request for Expression of Interest" (eoi/reoi), "Contract Award" (award), "General Procurement Notice" (gpn), "Invitation for Prequalification" (prequalification).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country filter — plain English name, e.g. \"Kenya\", \"Somalia\", \"Bangladesh\", \"Brazil\". Regional multi-country programs (e.g. \"Eastern and Southern Africa\") also match. Omit for worldwide."New value: +"Country filter, plain English name, e.g. \"Kenya\", \"Somalia\", \"Bangladesh\", \"Brazil\". Regional multi-country programs (e.g. \"Eastern and Southern Africa\") also match. Omit for worldwide."
    • changedInput schema / properties / method / description
      Previous value: -"Procurement method filter — code or name: RFB (Request for Bids), RFP (Request for Proposals), RFQ (Request for Quotations), INDV (Individual Consultant Selection), QCBS (Quality and Cost-Based Selection), LCS (Least Cost Selection), CQS (Consultant Qualification Selection), DIR (Direct Selection)."New value: +"Procurement method filter, code or name: RFB (Request for Bids), RFP (Request for Proposals), RFQ (Request for Quotations), INDV (Individual Consultant Selection), QCBS (Quality and Cost-Based Selection), LCS (Least Cost Selection), CQS (Consultant Qualification Selection), DIR (Direct Selection)."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "country": "Kenya",
      +    "limit": 10,
      +    "notice_type": "Invitation for Bids",
      +    "query": "solar panels"
      +  },
      +  {
      +    "limit": 20,
      +    "method": "RFP",
      +    "query": "water supply"
      +  }
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld and non-destructive, so the safety bar is low; the description still adds real value beyond them — ~412k notices ordered newest-first, keyless access, and the result shape (bid reference, project, deadline, public notice URL). It stops short of stating rate limits or result-count behavior when filters are broad.

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?

A single dense paragraph, front-loaded with what is searched, then filters, then result fields, then a keyless-source note — a sensible ordering with little waste. It is somewhat packed (notice-type enumeration could be trimmed since the schema repeats it), keeping it just under a top score.

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?

With six optional parameters, no output schema, and full schema coverage, the description supplies the missing pieces: corpus size, sort order, keyless auth, and the fields each result carries. Pagination is only covered by the schema's offset/limit descriptions, and sibling routing is not addressed, which leaves minor gaps.

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 the schema already documents every parameter including enum-like method codes and notice-type shorthands. The description only restates the filter set (country, notice type, method) without adding syntax, defaults, or interaction rules, so the baseline of 3 applies.

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 specific verb and resource (search World Bank procurement notices) and enumerates the notice categories covered — tenders, IFBs, EOIs, contract awards, GPNs — plus geography (~140 countries) and corpus size. It is clear what the tool returns, but it never differentiates itself from close siblings such as wb_procurement_awards or wb_procurement_by_country, whose scope it visibly overlaps.

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 guidance is limited to parameter-level hints embedded in the prose (filters for country/notice type/method) and the schema's 'omit to list latest notices'. There is no statement of when to choose this tool over the country-scoped or detail siblings, and no exclusions, so the agent must infer routing from names alone.

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.