Skip to main content
Glama

BRAINIAC Procurement Intelligence

Match company to opportunities

procurement-intelligence_match
Read-onlyIdempotent

Match a company profile against available procurement opportunities from UK Contracts Finder and Find a Tender with transparent scoring. Price $0.10 USDC. POST /api/v1/procurement-intelligence/match. 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": {
      "companyProfile": "<companyProfile>"
    },
    "name": "procurement-intelligence_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 50. Required.
publishedToNopublishedTo, string, date. Optional.
publishedFromNopublishedFrom, string, date. Optional.
companyProfileYescompanyProfile, object. Required.

Output Schema

NameRequiredDescriptionDefault
matchesNomatches. Array.
sourcesNosources. Array.
matchCountNomatchCount. Number.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
companyProfileNocompanyProfile. Object.

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, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new operational facts the annotations cannot convey: the $0.10 USDC price, the POST /api/v1/procurement-intelligence/match endpoint, and crucially that an unpaid call returns x402 payment terms without executing. That payment-gate disclosure is the most useful behavioral signal here.

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 the core matching action before the price, endpoint and payment-gate caveat. Nothing is redundant, though the endpoint path and price sit slightly apart from the functional sentence and could read as transport boilerplate.

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 present and full schema coverage, the description does not need to explain return values, and it correctly spends its space on the payment/auth gate instead. The only remaining gap is how 'transparent scoring' is composed and whether results span both data sources uniformly, which an agent would want to know before relying on ranking.

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 every field (companyProfile with name, cpvCodes, keywords, minValue/maxValue, locations, industries, capabilities, plus limit and the publishedFrom/publishedTo dates) is documented structurally. The description adds no meaning about how those fields influence scoring or matching, so the baseline 3 applies.

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 and resource ('Match a company profile against available procurement opportunities') plus the underlying data sources (UK Contracts Finder and Find a Tender) and the distinguishing trait of 'transparent scoring'. It does not explicitly contrast itself with siblings like procurement-intelligence_search or procurement-intelligence_opportunity, so an agent must infer that this is the profile-driven ranked-matching variant.

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 rather than stated: an agent can deduce it should call this when it has a structured company profile (cpvCodes, keywords, locations, value range) and wants ranked opportunities. There is no explicit when-not guidance and no named alternative for keyword-only or single-opportunity lookups, which are clearly present among the siblings.

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