Skip to main content
Glama

Worldbank Procurement

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Wb Procurement Awards

wb_procurement_awards
Read-onlyIdempotent

Search World Bank contract awards — which contracts were awarded under World Bank-financed development projects (300k+ award notices across developing countries). Filter by full-text keyword and/or country to see recently awarded goods, civil works, and consulting contracts, each with project, bid reference, procurement method, award publication date, and a public notice URL (the notice detail page names the awarded supplier). Newest first. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of awards to return (1-50). Default 10.
queryNoFull-text keyword, e.g. "bridge construction", "audit services", "medical equipment". Optional.
offsetNoResult offset for pagination. Default 0.
countryNoCountry name (plain English), e.g. "Kenya", "Ethiopia", "Vietnam". Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "Ethiopia",
+    "limit": 10,
+    "query": "bridge construction"
+  },
+  {
+    "limit": 25,
+    "offset": 0,
+    "query": "medical equipment"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description adds valuable behavioral details: results are sorted newest first, no authentication needed, and the result fields include a public notice URL. This goes beyond the annotations without contradicting them.

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?

The description is a single, front-loaded paragraph that efficiently conveys the core action, filtering options, result contents, ordering, and access requirements. Every sentence contributes meaningful information without redundancy.

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?

For a read-only search tool with four optional parameters and no output schema, the description covers functionality, filtering, result fields, ordering, and authentication. It lacks explicit explanation of pagination response structure but includes enough for effective usage.

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 coverage is 100%, and each parameter is already described in the input schema. The description restates that filtering is by keyword and country but does not add new semantic meaning beyond what the schema provides, achieving only the baseline score.

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 clearly states the tool searches World Bank contract awards, specifies the data scope (300k+ notices), and distinguishes it from sibling tools by focusing on award records rather than procurement details or country-specific searches.

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 provides context on when to use the tool (searching by keyword/country for awards) and mentions default ordering (newest first) and no API key requirement. However, it does not explicitly state when not to use it or name alternative tools.

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