Skip to main content
Glama

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

Procurement dossier, live tier (premium)

get_procurement_dossier_live
Read-only

Procurement dossier, live tier (premium). Premium live tier: the notice dossier re-pulled at call time. On the current snapshot build the live re-pull cannot complete, so the call serves the audited-snapshot dossier and names the degradation in the payload — no live freshness is claimed that was not performed. $5 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_dossier_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
notice_idYesrecord id from procurement-search (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/destructive annotations, the description discloses the degradation behavior (live re-pull cannot complete, payload names the degradation, no freshness claimed), the exact price and chain ($5 USDC on Base), and that the tool call itself is free while payment occurs on the returned URL. That is unusually rich behavioral disclosure that an agent needs before invoking a paid 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?

The content is front-loaded: tier and behavior first, then price and the x402 delivery flow. Every sentence carries information, though the leading restatement of the title ('Procurement dossier, live tier (premium)') is slightly redundant with the title field.

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 paid, currently-degraded tool with no output schema, the description covers everything an agent needs: what is returned (the x402 URL to GET), the payment handshake (402 → PAYMENT-SIGNATURE → delivery), the cost, and the honest disclosure that live freshness is not being delivered right now.

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?

With a single required parameter and 100% schema description coverage, the schema already documents notice_id as a 'record id from procurement-search'. The description adds no further meaning about the parameter, 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 ('the notice dossier re-pulled at call time') and labels the tier ('live', 'premium'), which lets an agent distinguish it from the snapshot-oriented siblings. However, the admission that the live re-pull currently cannot complete and serves the audited-snapshot dossier blurs the practical distinction from the snapshot sibling, so it stops short of a clean 5.

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?

It gives useful context about the paid flow ('Free to call this tool; payment happens on the URL') and the degradation behavior, which is implied guidance on what you will get. But it never explicitly says when to choose this live tier over a snapshot dossier sibling, and the degradation note means the practical selection criteria are left 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