Skip to main content
Glama

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

Procurement slice by agency

get_procurement_by_agency
Read-only

Procurement slice by agency. One agency slice of the Ni Biashara procurement shelf: active opportunities and recent awards for that agency in one call, counts by record type included. $0.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": {
      "agency": "<agency>"
    },
    "name": "get_procurement_by_agency"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax records to return (optional, default 25, max 60)
agencyYesagency name text, e.g. Veterans Affairs (required)
offsetNorecords to skip (optional, default 0)

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 declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered, but the description adds genuinely new behavior: the $0.1 USDC on Base price and the x402 handshake (402 → PAYMENT-SIGNATURE → delivery) with payment occurring on the returned URL rather than at call time. That is exactly the kind of auth/cost disclosure an agent cannot get from annotations. It stops short of describing result ordering, freshness of 'recent awards', or pagination behavior.

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?

Four short sentences, front-loaded with what the tool returns before moving to price and payment mechanics. Zero filler, though the phrase 'Ni Biashara procurement shelf' is unexplained brand jargon that consumes space without informing the agent.

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 at a high level (opportunities, awards, counts by record type), and it fully explains the payment flow an agent must handle. The remaining gap is what the returned x402 URL/payload actually looks like, but for a read-only lookup with fully documented params this is close to sufficient.

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% and all three parameters (agency, limit, offset) are documented with defaults and caps in the schema itself. The description adds no syntax, formatting, or matching guidance for the free-text 'agency' name, so it does not add meaning beyond the schema; baseline 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 names a specific resource scope — one agency's slice of procurement data — and enumerates the payload ('active opportunities and recent awards for that agency in one call, counts by record type included'). That is far more concrete than the bare title and implicitly separates it from the NAICS-scoped sibling. It stops short of explicitly naming which sibling to use instead, so it is clear but not fully differentiated.

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 by the phrase 'by agency'; nothing tells the agent when to use this over get_procurement_by_naics or search_procurement, nor whether it is a broad-discovery vs. lookup tool. It does clarify an important usage fact — that calling the tool is free and payment happens downstream — which is helpful but is about cost, not tool selection.

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