Skip to main content
Glama

Idb Get Notice

idb_get_notice
Read-onlyIdempotent

Fetch one IDB procurement notice by its notice id (from idb_search_notices results). Returns the full record: project, loan number, sector, procurement method, publication date, deadline, and the document URL on idbdocs.iadb.org. If the id has multiple entries (amendments/re-publications), all are returned newest-first.

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": {
      "notice_id": "38820"
    },
    "name": "idb_get_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
notice_idYesIDB notice id, e.g. "38846", find ids via idb_search_notices.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / notice_id / description
      Previous value: -"IDB notice id, e.g. \"38846\" — find ids via idb_search_notices."New value: +"IDB notice id, e.g. \"38846\", find ids via idb_search_notices."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavior: the multi-entry case where one id maps to amendments/re-publications and results come back newest-first, which an agent cannot infer from annotations. It omits not-found/error behavior, keeping it below the top mark.

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?

Three dense sentences: purpose first, payload second, edge case last. No filler or restatement of the name, and the caveat about multiple entries is placed exactly where a caller would look for it.

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 carries the burden and does so by enumerating the returned fields (project, loan number, sector, method, dates, document URL) and the ordering rule. The main remaining gap is what the agent should expect for an invalid or unknown id.

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% and the param already says ids come from idb_search_notices, so the baseline is 3. The description earns a bump by explaining that a single notice_id may resolve to several entries, which changes how the agent should interpret and consume the parameter value.

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?

States a specific verb and resource ('Fetch one IDB procurement notice') plus the keying mechanism ('by its notice id'), which cleanly separates it from the sibling idb_search_notices. The singular 'one' scopes it unambiguously.

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?

Explicitly routes the agent to idb_search_notices as the source of valid ids, establishing the search-then-fetch workflow. It stops short of stating when not to use it (e.g. for discovery or bulk listing), so it is clear context rather than full routing guidance.

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.