Skip to main content
Glama

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

Procurement notice dossier — competition context (premium)

get_procurement_notice_dossier
Read-only

Procurement notice dossier — competition context (premium). Premium: one procurement record plus the competition context a capture team actually pays for — incumbent recipient, prior award values for the same NAICS or agency, a re-compete flag from period-of-performance end dates, and days to deadline, joined from the awards dataset at serve time. $2.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_notice_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
notice_idYesrecord id from procurement-search (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, non-destructive, so the description adds genuinely new behavioral facts: the $2.5 USDC price on Base, the x402 flow (402 → PAYMENT-SIGNATURE → delivery), that calling the tool itself is free with payment occurring on the returned URL, and that context is joined at serve time. Only failure/refund or delivery-timeout behavior is left unstated.

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?

Content is front-loaded: what the dossier contains comes first, pricing and the delivery flow after. The only waste is restating the name/title verbatim at the opening, which duplicates an already-supplied structured field.

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 describing returns and does so — it enumerates the joined fields and states the return value is an x402 URL to GET. Enough to call correctly; only edge-case behavior (expired payment, partial data) is unaddressed.

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 coverage is 100% and the single notice_id is documented as 'record id from procurement-search (required)'. The description adds no further meaning about the parameter, which is acceptable at the baseline given the schema does the work.

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?

Names a specific resource (a procurement notice dossier) and enumerates the concrete payload — incumbent recipient, prior award values by NAICS/agency, re-compete flag, days to deadline — so the agent knows exactly what it gets. It does not explicitly separate itself from near-name siblings such as get_procurement_notice_plus or get_procurement_dossier_live, so it stops short of 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?

The framing 'the competition context a capture team actually pays for' implies the use case (competitive capture analysis on a single notice) and the payment mechanics tell the agent it is a paid path. However, there is no explicit when-to-use/when-not or naming of which cheaper sibling to prefer for a plain record, leaving the alternative choice 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