SiteCheck Trade & Energy

Asian Development Bank procurement notices: notice title

energy_adb_procurement_notices

Read-only

Asian Development Bank procurement notices (the newest 12 tenders, optionally filtered by keyword and country): notice title with project number, notice type (e.g. Invitation for Bids), status, bid deadline, country/economy, sector, posting date, loan/grant approval numbers and the notice document link. From adb.org/projects/tenders via a rendering residential proxy. Related tools on this server, for a different need: energy_world_bank_procurement when you need World Bank funded projects by country from the World Bank. Price: $0.02 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
`query`	No	Optional keyword matched in title, sector and notice type, e.g. water, road, solar
`country`	No	Optional country/economy, e.g. Pakistan, Bangladesh

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior the agent could not otherwise know: the hard cap of 12 newest tenders, retrieval via a rendering residential proxy at adb.org/projects/tenders, and a metered cost of $0.02 USDC per successful call under x402 with failed calls not charged. Cost and cap disclosure directly affect whether and how an agent should call this tool.

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?

Front-loaded with the resource and the 12-item scope, then the alternative, then pricing, in a logical order. The long enumeration of returned fields is somewhat wasteful given an output schema exists, but the sentences are information-dense rather than padded.

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 scope, source, filters, cost, and the sibling alternative, and an output schema exists so the field list need not be spelled out in prose. The only real gap is the absence of any note that the 12-item cap makes this unsuitable as an exhaustive tender search; spending the field enumeration on that caveat would have been stronger.

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 both optional parameters (query, country) are already documented including examples and match fields. The description only restates 'optionally filtered by keyword and country' and adds no new syntax, defaults, or combination rules, 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+resource (Asian Development Bank procurement notices), the exact scope (the newest 12 tenders, optionally filtered by keyword and country), and enumerates what each notice carries. It also names the sibling energy_world_bank_procurement as the different-source alternative, so an agent can distinguish the two 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?

Gives a clear routing rule: use this for ADB tenders, use energy_world_bank_procurement when the need is World Bank funded projects by country. It does not state exclusions beyond that (e.g. that results are capped at 12 so it is not a comprehensive tender search), but the context for use is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Trade & Energy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?