Skip to main content
Glama

Idb Search Notices

idb_search_notices
Read-onlyIdempotent

Search Inter-American Development Bank (IDB) project procurement notices, live bidding notices, expressions of interest, general/specific procurement notices, and contract-award notifications for IDB-financed projects across 26 Latin American and Caribbean countries. Filter by country, sector, and keyword; defaults to open notices only (deadline not yet passed) sorted soonest-first. Each result carries the notice id, project, deadline, and a document URL. Keyless, ~37,000 notices, queried live.

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": 5,
      "country": "Peru",
      "open_only": true
    },
    "name": "idb_search_notices"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoNotice type filter: "specific" (specific procurement notice), "general" (general procurement notice), "eoi" (expression of interest), "award" (contract award notification), or "rfi" (request for information). Omit for all types.
limitNoMax notices to return (1-50). Default 15.
sectorNoSector keyword, e.g. "Energy", "Health", "Transport", "Water". Partial/case-insensitive match against the English sector name.
countryNoCountry name, e.g. "Peru", "Ecuador", "Jamaica". Partial/case-insensitive match. Omit for all LAC countries.
keywordNoFull-text keyword against the notice title and project name, e.g. "road rehabilitation", "software licenses".
open_onlyNoRestrict to notices whose deadline has not passed (default true). Set false to include closed/expired notices too, or when type is "award" (awards have no future deadline).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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/non-destructive, so the description is not the sole source of the safety profile. It nonetheless adds genuinely new behavioral facts beyond annotations: no API key required, roughly 37,000 notices in the corpus, live querying, and the default deadline filter with soonest-first ordering — all decision-relevant for an agent.

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?

Three sentences, front-loaded with the resource and scope, followed by filtering defaults and return shape — no filler. The opening sentence is somewhat padded by enumerating five notice categories that the 'type' parameter already enumerates, which is minor redundancy rather than noise.

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 no output schema, the description steps in and names the returned fields (notice id, project, deadline, document URL), and it discloses auth-free access and corpus scale. That covers nearly everything needed to call it correctly; only pagination behavior beyond the limit range is left implicit.

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%, so every parameter is already documented in the input schema and the baseline of 3 applies. The description restates only that filtering is available on country, sector, and keyword plus the open-only default; it adds no syntax or matching-rule detail (e.g. partial matching, limit range) beyond what the schema already provides.

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 gives a specific verb ('Search') and a well-scoped resource (IDB procurement notices) and enumerates the notice categories covered, so an agent knows exactly what corpus is being queried. It does not, however, distinguish itself from the sibling idb_search_awards, which overlaps with the 'contract-award notifications' mentioned here, leaving a potential ambiguity for an agent choosing between the two.

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 establishes useful operating context: filtering by country/sector/keyword and a default of open notices sorted soonest-first. What it lacks is explicit routing guidance — when to prefer this over idb_search_awards for awards or idb_get_notice for a single notice — so the agent must infer the boundary from the sibling 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.