Skip to main content
Glama

BRAINIAC Corporate Ownership, Sanctions & Investigation

Check public procurement exclusions

corporate-intelligence_public-procurement-exclusion-check

Compare companies to a supplied procurement exclusion list. Only exact name or registry matches are confirmed exclusions. Price $0.04 USDC. POST /api/v1/corporate-intelligence/public-procurement-exclusion-check. Unpaid calls return 402 and do 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": "corporate-intelligence_public-procurement-exclusion-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
companiesNo
directorsNo
fetchOfacNo
ownershipNo
exclusionsNo
nameVariantsNo
relationshipsNo
sanctionsEntriesNo
enforcementRecordsNo
previousSanctionsEntriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose several useful traits: a per-call price ($0.04 USDC), the POST endpoint, 402 on unpaid calls with no execution, and that only exact name or registry matches count as confirmed exclusions (i.e., no fuzzy matching). It does not cover what the response contains, whether results are cached, rate limits, or how the many optional arrays are combined.

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?

Four short sentences, front-loaded with the purpose and followed by the matching rule, price, and payment failure behavior. Nothing is padded, though the raw endpoint string adds little for an agent already calling the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a high-complexity tool: 15 optional parameters, deep nested objects, no annotations, and no output schema. Given that surface area, the description is too thin — an agent cannot tell which input channel to use, how inputs combine, or what a confirmed vs unconfirmed exclusion looks like in the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 15 parameters, several of them nested arrays, so the description must compensate and mostly does not. It only hints at 'companies' and a supplied exclusion list, leaving csv/json/text/file, asOf, fetchOfac, directors, ownership, nameVariants, relationships, sanctionsEntries, and previousSanctionsEntries entirely unexplained.

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: 'Compare companies to a supplied procurement exclusion list.' The added clause on exact name/registry matching sharpens what the tool actually confirms. It never names a sibling (e.g., company-enforcement-history or sanctions-list-change-detect) to draw the boundary, so an agent must infer the distinction.

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: use it when you have a list of companies to screen against an exclusion list you supply yourself. There is no explicit when-not guidance, no mention of prerequisites such as required input shape, and no routing to related sanction/enforcement tools for adjacent questions.

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