Skip to main content
Glama

BRAINIAC Procurement Intelligence

Get opportunity details

procurement-intelligence_opportunity
Read-onlyIdempotent

Retrieve full details of a procurement opportunity by OCID from UK Contracts Finder or Find a Tender. Price $0.03 USDC. POST /api/v1/procurement-intelligence/opportunity. 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": {
      "ocid": "<ocid>"
    },
    "name": "procurement-intelligence_opportunity"
  }
}

Input Schema

NameRequiredDescriptionDefault
ocidYesocid, string, length 1 to 100. Required.

Output Schema

NameRequiredDescriptionDefault
ocidNoocid. String.
foundNofound. Boolean.
sourceNosource. String.
sourcesNosources. Array.
limitationsNolimitations. Array.
opportunityNoopportunity. Object.
retrievedAtNoretrievedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations cover the read-only/idempotent safety profile, but the description adds behavior annotations do not: a concrete price ($0.03 USDC), the x402 payment mechanism, and the critical fact that an unpaid call returns payment terms rather than data. This is exactly the kind of operational detail an agent needs before invoking a paid endpoint.

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 with zero filler, front-loaded with purpose, then cost, then the endpoint path, then the gating condition. The endpoint path is arguably redundant but is compact and useful for debugging.

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-value detail is unnecessary, and the description covers cost, payment gating, and sources. It stops short of stating wallet/auth prerequisites for x402 settlement or error behavior when an OCID is not found, which would round out a paid-tool definition.

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% and the single 'ocid' parameter is fully documented (type, length bounds, required). The description adds no format detail beyond the schema (e.g., OCID prefixes or validation rules), so it sits at the baseline where the schema does the work.

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 full details of a procurement opportunity by OCID') and names both underlying sources (UK Contracts Finder, Find a Tender). The 'by OCID' framing implicitly separates it from the search/list siblings (procurement-intelligence_search, _awards), but no sibling is named, so the differentiation is inferred rather than stated.

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 only implied: it is the tool to call when you already hold an OCID. There is no explicit guidance on how to obtain an OCID (e.g., via the search sibling) or when to prefer a search tool instead. The note that an unpaid call does not execute gives useful context about invocation conditions but is not routing guidance.

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