Skip to main content
Glama

Check names against debarment and exclusion lists

screen_debarment
Read-only

Searches the World Bank Listing of Ineligible Firms and Individuals for debarred and ineligible firms and individuals. Each hit: list, name, country, grounds, from/to dates, source URL. If a list is unreachable, returns listsUnavailable and 503 when none are checked. Related tools on this server, for a different need: screen_export_control when you need to check names against the US Consolidated Screening List. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "screen_debarment"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName or keyword to search (1–200 characters)
limitNoMax results per source (1–50, default 20)
countryNoOptional ISO-2 country code filter

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
resultsNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint by disclosing the per-hit return fields, the partial-failure signal (listsUnavailable) and the 503-when-nothing-checked behavior, plus pricing and that failed calls are not charged. That is exactly the kind of operational context annotations cannot carry.

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?

Front-loaded with purpose and result shape, then failure behavior, then the alternative, then cost. The payment sentence is dense but each clause (per-call price, mechanism, no charge on failure) is decision-relevant.

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?

Covers purpose, result contents, failure modes, cost, and sibling routing; with an output schema present, the description need not document return structure further. Minor gaps remain around zero-result handling and how the country filter interacts with multi-source results.

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% (name, limit, country all documented inline), so parameter meaning is already handled by the schema. The description adds no syntax or filtering nuance beyond what the schema states, so baseline 3 applies.

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 ("Searches") and a specific, named resource ("World Bank Listing of Ineligible Firms and Individuals"), and explicitly contrasts itself with screen_export_control so an agent can route without opening either 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?

Names the alternative tool and the condition that selects it (US Consolidated Screening List checks), which gives clear routing context. It does not spell out any other exclusions or when this source would be inappropriate, but the primary ambiguity is resolved.

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.

Resources