Skip to main content
Glama

Worldbank Procurement

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON 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. 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"
+  }
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, openWorldHint. The description adds behavioral context: results sorted newest first, keyless access, and global multilateral source. No contradictions.

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 informative and front-loaded, but slightly verbose with extra details like '~412k notices'. Could be tighter without losing value.

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?

For a search tool with no output schema, the description fully covers purpose, filters, ordering, and return fields (bid reference, project, deadline, URL). It provides examples and notes keyless access, making it very complete.

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%. The description adds meaning beyond the schema by explaining query as full-text, country as plain English, notice_type with shorthand. Examples further clarify usage.

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 clearly states it searches World Bank procurement notices with full-text and filters, listing notice types and regions. However, it does not explicitly differentiate from sibling tools like wb_procurement_awards or wb_procurement_by_country, though the search capability is implied as distinct.

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 description explains how to use filters and search, but does not provide explicit when-to-use or when-not-to-use guidance versus sibling tools. Alternatives are not mentioned.

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

All Worldbank Procurement toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources