Skip to main content
Glama

BRAINIAC Procurement Intelligence

Search procurement opportunities

procurement-intelligence_search
Read-onlyIdempotent

Search UK procurement opportunities from Contracts Finder and Find a Tender with filtering by date, stage, keyword, CPV, location, and value. Price $0.02 USDC. POST /api/v1/procurement-intelligence/search. 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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 100. Required.
cursorNocursor, string, length 0 to 200. Optional.
stagesNostages, array. Optional.
cpvCodeNocpvCode, string, length 0 to 20. Optional.
keywordNokeyword, string, length 0 to 200. Optional.
locationNolocation, string, length 0 to 100. Optional.
maxValueNomaxValue, number, from 0 to any. Optional.
minValueNominValue, number, from 0 to any. Optional.
publishedToNopublishedTo, string, date. Optional.
publishedFromNopublishedFrom, string, date. Optional.

Output Schema

NameRequiredDescriptionDefault
queryNoquery. Object.
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
resultCountNoresultCount. Number.
retrievedAtNoretrievedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the bar is lower, and the description adds genuinely non-obvious behavior: a $0.02 USDC charge, the POST endpoint, and that an unpaid call returns x402 payment terms without executing. That pre-call failure mode is exactly the kind of context the agent needs; only rate limits or result volume behavior are absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, no filler, with the core capability front-loaded and the cost/payment caveat placed afterward where it will still be read before 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?

With an output schema, rich annotations, and fully documented parameters, the description needs only to cover routing and cost, which it does. Pagination semantics for the cursor parameter are the only notable omission.

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 schema carries the parameter burden and the baseline applies. The description's list of filterable dimensions (date, stage, keyword, CPV, location, value) mirrors the schema without adding semantics such as keyword matching rules or whether ranges are inclusive.

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 ('Search UK procurement opportunities'), names the two underlying sources (Contracts Finder, Find a Tender), and enumerates the filter dimensions. The 'UK' scope plus sources distinguishes it cleanly from the EU-notices and US-awards siblings.

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 description establishes context (UK public procurement, what can be filtered) but gives no explicit when-to-use/when-not guidance and no routing to alternatives such as the single-opportunity or buyer lookups. Usage is implied rather than instructed.

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