Skip to main content
Glama

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

Procurement slice by NAICS code

get_procurement_by_naics
Read-only

Procurement slice by NAICS code. One NAICS slice of the Ni Biashara procurement shelf: active opportunities and recent awards for that code in one call. SAM summary records carry no NAICS, so v1 slices are award-led and say so in the payload. $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": {
      "naics": "<naics>"
    },
    "name": "get_procurement_by_naics"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax records to return (optional, default 25, max 60)
naicsYesNAICS code, e.g. 541512 (required)
offsetNorecords to skip (optional, default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly, openWorld, non-destructive) by disclosing the payment model ($0.1 USDC on Base), the exact handshake (402 → PAYMENT-SIGNATURE → delivery), and the fact that the call itself is free while payment occurs at the returned URL. It also flags a data limitation — SAM summary records carry no NAICS so v1 slices are award-led and say so in the payload — which an agent could not learn from annotations.

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?

Purpose is front-loaded in the first sentence, followed by scope, the data caveat, pricing, and the return mechanism in a logical order with no filler. Slightly dense with domain jargon ('procurement shelf', 'Ni Biashara') and the payment/logistics sentences could be tightened, but nothing is wasted.

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 correctly carries the burden of explaining what comes back: an x402 URL to GET rather than records directly, plus the payment steps and a note that the payload self-documents its award-led nature. Rate limits and pagination behavior for the returned endpoint are the only meaningful omissions for a paid open-world tool.

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 naics, limit, and offset are already documented with defaults and caps; baseline 3 applies. The description adds one genuinely new semantic point — that NAICS coverage is absent from SAM summary records, which affects what the code actually matches — but gives no format or syntax guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Procurement slice by NAICS code') plus the exact scope: active opportunities and recent awards for one code in a single call. The 'one NAICS slice' framing and the sibling name get_procurement_by_agency make the axis of slicing unambiguous without needing the schema.

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?

Implies when to use it ('for that code in one call') and explains the award-led limitation of v1 slices, which is a useful selection caveat. But it never names an alternative (e.g., search_procurement or the agency slice) or states when-not to use this tool, so the choice is 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