Skip to main content
Glama

Idb Check Mdb Debarment

idb_check_mdb_debarment
Read-onlyIdempotent

Check whether a person or firm name appears on the multilateral development bank cross-debarment list, IDB's own debarment/sanctions list PLUS the cross-debarred lists of the World Bank Group, Asian Development Bank, African Development Bank, and EBRD, which the five banks mutually enforce. Answers "is this vendor debarred" for procurement due-diligence. Matching is accent- and case-insensitive (handles Spanish/Portuguese diacritics like "González" vs "Gonzalez") and requires every word of the query name to appear in a record, so a full name narrows results, a bare surname broadens them. Returns each match's entity type, nationality, sanction dates, prohibited practice, and which bank's list it came from. Keyless, ~1,300 records, 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": {
      "name": "Ricardo Reynoso Gonzalez"
    },
    "name": "idb_check_mdb_debarment"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPerson or firm name to check, e.g. "Ricardo Reynoso Gonzalez" or "Consultora Tecnodinamica". Accents optional.
limitNoMax matches to return (1-50). Default 10.
sourceNoOptional filter to one issuing bank, e.g. "IDB", "WBG", "ADB", "AfDB", "EBRD" (partial match against the source label).
entity_typeNoOptional filter: "Individual" or "Firm".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantive behavior beyond them: keyless access, ~1,300 records, live querying, accent/case-insensitive matching with an all-words-must-match rule, and the fields returned per match. It also states the practical consequence of the matching rule (full name narrows, bare surname broadens), which is exactly the context an agent needs to phrase a query.

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 first sentence leads with the core action and scope, follow-ups add matching behavior, return fields, and scale in order of usefulness. It is dense but nearly every clause carries decision-relevant information; the bank-name enumeration is the one stretch that could be compressed without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-record lookup with no output schema, the description supplies everything needed: data provenance (five mutually enforcing banks), dataset size, freshness (queried live), matching rules, and the shape of matches (entity type, nationality, sanction dates, prohibited practice, source list). An agent can call it and interpret results without further inference.

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%, so the baseline is 3; the description earns above that by explaining the matching semantics of the `name` parameter — diacritic folding and the AND-over-words behavior — which is not derivable from the schema's example-based description. The limit, source, and entity_type filters are left entirely to the schema, which is acceptable given full coverage.

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 names a specific verb and resource: check whether a person or firm name appears on the MDB cross-debarment list, and enumerates which five banks' lists are covered. It also frames the question it answers ("is this vendor debarred"), so an agent can distinguish it from unrelated siblings like company_register_search or ai_visibility_check without opening the schema.

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?

Usage context is explicit: procurement due-diligence and the "is this vendor debarred" question. What is missing is any exclusion or alternative-tool routing — e.g. what to use for a company profile or general registry lookup instead — though no sibling appears to overlap directly with debarment screening.

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.