Skip to main content
Glama

BRAINIAC Corporate Ownership, Sanctions & Investigation

Build investigation source citation package

corporate-intelligence_investigation-source-citation-package

Aggregate registry, ownership, sanctions, enforcement, exclusion, and network summaries with source citations. Uncertain matches stay unconfirmed. Price $0.08 USDC. POST /api/v1/corporate-intelligence/investigation-source-citation-package. 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_investigation-source-citation-package"
  }
}

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

C2.9/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does add real operational facts: $0.08 USDC cost, POST endpoint, 402 on unpaid calls with no execution, and the rule that uncertain matches remain unconfirmed. It still omits conflict resolution across the aggregated sources, whether any input mode takes precedence, and how large a 15-parameter payload behaves in practice.

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, front-loaded sentences with no filler; the aggregation scope leads and the payment/error terms follow. The brevity is well organized, though part of it comes at the cost of the missing parameter guidance noted elsewhere.

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 parameters, nested object arrays, no output schema, and no annotations. Against that, the description leaves input mode selection, cross-array linking, and result shape entirely unexplained, so an agent cannot confidently construct a call from the definition alone.

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, so the description must compensate and largely fails to. The aggregated categories (sanctions, ownership, enforcement, exclusions) loosely echo input array names, and 'Uncertain matches stay unconfirmed' hints at matching behavior, but nothing explains csv vs json vs text vs file, asOf, fetchOfac, or the id-linkage fields that tie the arrays together.

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 names a specific verb ('Aggregate') plus the resource classes it combines (registry, ownership, sanctions, enforcement, exclusion, network summaries) with source citations. That is a clear picture of what the tool produces. It does not explicitly contrast itself with the individual sibling tools that cover those same domains one by one, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given, and no alternatives are named. The description never says whether to call this instead of the per-domain siblings (sanctions-list-change-detect, company-ownership-chain-map, etc.) or in addition to them. The only conditional information is payment-related, not usage-related.

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