Skip to main content
Glama

Worldbank Procurement

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.

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": 15,
      "country": "Nigeria",
      "notice_type": "Contract Award"
    },
    "name": "wb_procurement_by_country"
  }
}

Input 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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description does add useful context beyond them: result ordering ("Newest first"), the returned fields (bid reference, project name, deadline, method, notice URL), and that access is "Keyless." It stops short of noting rate limits, pagination, or behavior when a country has no notices.

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 purpose is front-loaded in the first clause, followed by output shape and then use case. It is somewhat dense and enumerates notice types in the description while the schema enumerates them again, but no sentence is filler.

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 three-parameter read-only lookup with full schema coverage and no output schema, the description carries what matters: return ordering, fields, access model, and geographic scope. Missing only minor operational detail such as behavior on unknown countries or result truncation.

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 all three parameters including the notice_type variants and the limit range are already documented in structured data. The description reinforces the country scoping and notice-type scope but adds no syntax, format, or edge-case meaning beyond the schema, so baseline 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 ("List the latest World Bank procurement notices") and scopes it to "one developing country," then enumerates the notice types covered (tenders, IFBs, EOIs, contract awards). It does not name a sibling, so an agent must infer how this differs from wb_procurement_search or wb_procurement_awards from scope language alone.

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?

It states a use context ("finding active bidding opportunities or recent government contract activity") and a geographic frame, which implies when to reach for it. However, it offers no explicit when-not guidance and never routes the agent to the obvious alternatives, even though several procurement siblings exist.

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.