Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

One procurement record, enriched (premium)

get_procurement_notice_plus
Read-only

One procurement record, enriched (premium). Premium: one notice or award from the Ni Biashara procurement shelf in full — every field its source publishes, with any enrichment gaps named in the payload rather than padded. Served from the audited snapshot with its as_of stamp. $1 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

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

Input Schema

NameRequiredDescriptionDefault
notice_idYesrecord id from procurement-search (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, the description discloses the payment model in detail: free to call, $1 USDC on Base, and a returned x402 URL that resolves via 402 → PAYMENT-SIGNATURE → delivery. It also states that enrichment gaps are named rather than padded and that results carry an as_of stamp from an audited snapshot, which is exactly the kind of behavioral context annotations cannot convey.

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 definition is front-loaded with the core purpose and then the payment mechanics, and every sentence carries operational information. There is mild redundancy in restating the title and the 'premium' label at the start, but no filler.

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 of explaining the return value, and it does: the tool returns an x402 URL to GET rather than the record itself. Combined with the freshness stamp note, an agent knows what to expect, though the shape of the final delivered payload is described only loosely.

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?

There is a single parameter with 100% schema coverage, and the schema already explains that notice_id is a record id from procurement-search. The description adds no format, prefix, or validation detail beyond that, so the baseline of 3 applies.

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 states a specific verb and resource: fetch one notice or award in full from the Ni Biashara procurement shelf, sourced from an audited snapshot. It is clear what the tool returns, but it never mentions the closely named sibling get_procurement_notice_dossier, so an agent must infer the difference between the 'plus' and 'dossier' variants.

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?

Usage is only implied: the notice_id must come from procurement-search, and the tool is for retrieving a single record in full. There is no explicit when-to-use or when-not-to-use statement relative to search_procurement or the dossier siblings, leaving selection to inference.

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