Skip to main content
Glama

Worldbank Procurement

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Wb Procurement By Country

wb_procurement_by_country
Read-onlyIdempotent

List the latest World Bank procurement notices for one developing country — open tenders, invitations for bids, expressions of interest, and contract awards funded by World Bank international development projects there. Newest first with bid reference, project name, submission deadline, procurement method, and public notice URL. Useful for finding active bidding opportunities or recent government contract activity in countries across Africa, Asia, and Latin America. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of notices to return (1-50). Default 15.
countryYesCountry name (plain English), e.g. "Kenya", "Nigeria", "India", "Ukraine". Required.
notice_typeNoOptional notice type: "Invitation for Bids", "Request for Expression of Interest", "Contract Award", "General Procurement Notice", or "Invitation for Prequalification" (shorthands like "bids", "eoi", "award" also accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "Nigeria",
+    "limit": 15,
+    "notice_type": "Contract Award"
+  },
+  {
+    "country": "Bangladesh"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds valuable context: keyless access, 'newest first' ordering, and that it covers notices from World Bank projects. No contradictions with annotations.

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?

Two concise sentences that front-load the purpose and key details. Every sentence adds value with no 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?

Without an output schema, the description explains the return format including bid reference, project name, submission deadline, etc. It covers the essential context for a list tool with three well-documented parameters.

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% with descriptions for all three parameters. The description adds little beyond schema: mentions 'newest first' ordering and keyless access but doesn't elaborate on parameter semantics. Baseline score of 3 is appropriate.

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 lists latest World Bank procurement notices for a developing country, specifying types (open tenders, invitations, etc.) and output fields. It distinguishes itself from siblings like wb_procurement_awards and wb_procurement_search by focusing on listing all notices by country.

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 implies usage for finding bidding opportunities or contract activity, but lacks explicit guidance on when not to use it or comparisons with sibling tools. The phrase 'useful for' suggests context but no exclusions or alternatives are 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