Skip to main content
Glama

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

Procurement daily brief

get_procurement_daily_brief
Read-only

Procurement daily brief. The procurement day in one call from the Ni Biashara procurement shelf: snapshot counts, the nearest deadlines sorted ascending with timezones, and the top agencies by record count, computed from the current snapshot at serve time. $0.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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds critical context beyond that: data is 'computed from the current snapshot at serve time,' the tool costs $0.5 USDC on Base, and it returns an x402 URL requiring GET with a 402 → PAYMENT-SIGNATURE → delivery flow. It also clarifies the tool call itself is free and payment occurs on the returned URL. This is rich behavioral disclosure.

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 description is four sentences and largely front-loaded with purpose and contents. The first sentence ('Procurement daily brief') is redundant with the title and name, but the remaining sentences are dense and earn their place by covering data contents, cost, and payment flow.

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?

Given zero parameters, no output schema, and annotations that cover safety, the description is nearly complete. It explains what data is returned (snapshot counts, deadlines, top agencies), that it is computed at serve time, and that the return value is an x402 URL with a specific payment flow. It could further describe the structure of the URL payload, but for a simple daily brief tool this is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain. The schema is empty and fully described. Baseline 4 applies for a zero-parameter tool.

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 specifies the resource and its contents: 'snapshot counts, the nearest deadlines sorted ascending with timezones, and the top agencies by record count.' This distinguishes it from sibling daily briefs (cyber, diaspora, fx) by domain and from procurement detail tools. The opening 'Procurement daily brief' restates the title, but the following sentence adds concrete detail.

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 phrase 'The procurement day in one call' implies this is an aggregated overview tool, but the description never explicitly states when to use it versus alternatives like search_procurement or get_procurement_by_agency. No exclusions or alternative routing are given.

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