Skip to main content
Glama

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

Federal procurement search — opportunities + awards

search_procurement
Read-only

Federal procurement search — opportunities + awards. Filtered search over the Ni Biashara procurement shelf: SAM.gov contract opportunities and USAspending contract awards as normalized, joined records with structured deadlines. Filter by text, agency, NAICS, set-aside, record type, deadline window or value floor. $0.25 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

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": "search_procurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNofree text over title, agency, description, recipient and solicitation id (optional)
typeNoopportunity or award (optional)
limitNomax records to return (optional, default 25, max 60)
naicsNoNAICS code, e.g. 541512 (optional)
agencyNoagency name text, e.g. Department of Veterans Affairs (optional)
offsetNorecords to skip (optional, default 0)
set_asideNoset-aside value on the record (optional)
min_value_usdNoonly records valued at or above this many USD (optional)
closing_within_daysNoonly records with a deadline within this many days (optional)

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 cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint true), and the description still adds real context beyond them: a $0.25 USDC on Base price, and the concrete payment handshake (402 → PAYMENT-SIGNATURE → delivery) with the clarification that the tool call itself is free. That is meaningful disclosure for a paid endpoint. It stops short of describing rate limits, failure modes, or result format depth, so it is not a 5.

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?

Dense and front-loaded: what it searches, what filters exist, then cost and payment mechanics in that order. The closing pair ('Returns the x402 URL to GET...' and 'Free to call this tool; payment happens on the URL') restates the same commercial fact twice, which is the only real waste.

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?

For a 9-parameter, all-optional search tool with no output schema, the description covers the domain, the record types, the filter surface, and the payment/return contract (a URL to GET). An agent can call it and knows what comes back at a high level. It does not explain pagination behavior or what the delivered payload looks like, which keeps it below full marks.

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 every one of the nine parameters is already documented in the schema. The description enumerates the same filter set (text, agency, NAICS, set-aside, record type, deadline window, value floor) but adds no syntax, format, or interaction detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb and resource ('Filtered search over the Ni Biashara procurement shelf') and scopes it to SAM.gov opportunities plus USAspending awards as joined normalized records. It is clear about what it covers, but never names the adjacent siblings (get_procurement_by_agency, get_procurement_by_naics, get_procurement_notice_dossier) that an agent would weigh against it.

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 lists the filterable dimensions and states the tool is free to call with payment happening downstream, which implies when the tool is appropriate. However, there is no explicit when-to-use versus when-not-to-use guidance, and no routing statement pointing to the per-agency, per-NAICS, or dossier siblings for narrower or deeper lookups.

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