Skip to main content
Glama

BRAINIAC Procurement Intelligence

Get awarded contracts

procurement-intelligence_awards
Read-onlyIdempotent

Retrieve awarded contracts and suppliers from UK Contracts Finder and Find a Tender by OCID or buyer ID. Price $0.05 USDC. POST /api/v1/procurement-intelligence/awards. An unpaid call returns the x402 payment terms and does not run.

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": "procurement-intelligence_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
ocidNoocid, string, length 1 to 100. Optional.
limitNolimit, integer, from 1 to 100. Required.
buyerIdNobuyerId, string, length 1 to 100. Optional.

Output Schema

NameRequiredDescriptionDefault
ocidNoocid. Null.
awardsNoawards. Array.
buyerIdNobuyerId. String.
sourcesNosources. Array.
awardCountNoawardCount. Number.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.

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 readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds genuinely new behavior: a $0.05 USDC cost and the fact that an unpaid call returns x402 payment terms without executing. That payment-gate detail is exactly the kind of non-obvious behavior an agent needs. It does not describe result shape or pagination, but an output schema exists, so the gap is small.

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 what the tool does, followed by cost and the payment-gate caveat. Every sentence carries information, though the raw POST endpoint path is marginally redundant for a structured tool invocation.

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?

The tool is a read-only retrieval with a full output schema, so return-value explanation is not required. The description covers sources, keys, cost, and the unpaid-call failure mode, leaving only minor gaps such as result volume and the effect of the limit parameter.

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 the baseline is 3. The description adds one useful nuance not in the schema: ocid and buyerId are alternative lookup paths ('by OCID or buyer ID'), which conveys disjunctive rather than conjunctive use. The limit parameter and default/maximum bounds are left entirely to the schema.

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 (Retrieve) plus the resource (awarded contracts and suppliers) and names the two data sources (UK Contracts Finder and Find a Tender) along with the lookup keys (OCID or buyer ID). This implicitly separates it from the US and EU siblings, but it never explicitly states that it is the UK-only tool or names an alternative to use for other jurisdictions.

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 through the named sources and lookup keys, so an agent can infer this is the route for UK award lookups by OCID or buyer ID. There is no explicit when-to-use, when-not-to-use, or named alternative from the sibling set (e.g. the US or EU award tools), leaving routing partly 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