Skip to main content
Glama

BRAINIAC Procurement Intelligence

Get buyer procurement history

procurement-intelligence_buyer
Read-onlyIdempotent

Retrieve procurement history for a buyer from UK Contracts Finder and Find a Tender. Price $0.05 USDC. POST /api/v1/procurement-intelligence/buyer. An unpaid call returns the x402 payment terms and does not run.

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": {
      "buyerId": "<buyerId>"
    },
    "name": "procurement-intelligence_buyer"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 100. Required.
buyerIdYesbuyerId, string, length 1 to 100. Required.

Output Schema

NameRequiredDescriptionDefault
buyerIdNobuyerId. String.
sourcesNosources. Array.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
opportunitiesNoopportunities. Array.
opportunityCountNoopportunityCount. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: a $0.05 USDC cost and the fact that an unpaid call returns x402 payment terms and does not execute — an important failure mode an agent must anticipate.

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?

Three short sentences, front-loaded with purpose followed by cost and payment semantics; nothing is padded. The raw endpoint path 'POST /api/v1/procurement-intelligence/buyer' is the least valuable element and could be dropped, but it does not obscure the message.

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?

An output schema exists, so return values need not be described, and the payment/failure behavior — the hardest thing for an agent to guess — is disclosed. The remaining gap is the identifier semantics of buyerId, which an agent must know to call correctly on the first try.

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 both buyerId and limit are already documented in the schema, setting the baseline at 3. The description adds no meaning beyond the schema — it does not clarify whether buyerId is a name, an internal ID, or a Companies House number, nor how limit interacts with the result set.

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?

States a specific verb and resource ('Retrieve procurement history for a buyer') and names the two underlying data sources (UK Contracts Finder, Find a Tender), which scopes it well against the US-focused siblings. It stops short of explicitly differentiating itself from siblings like procurement-intelligence_search or _awards.

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 implied by the resource ('for a buyer') and the payment note tells the agent an unpaid call returns x402 terms rather than data, which is real operational context. However, there is no explicit when-to-use guidance or statement of which sibling to choose when the task could also be served by a broad search tool.

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