Skip to main content
Glama

BRAINIAC Corporate Ownership, Sanctions & Investigation

Map company ownership chains

corporate-intelligence_company-ownership-chain-map

Walk supplied parent-child ownership edges into chains. Missing ownership percents are labeled, not invented. Price $0.05 USDC. POST /api/v1/corporate-intelligence/company-ownership-chain-map. 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_company-ownership-chain-map"
  }
}

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, the description carries the full burden, and it does disclose real behavior: missing ownership percents are labeled rather than imputed, the call costs $0.05 USDC, and unpaid calls return 402 without running. That is meaningful for a paid endpoint. However, it says nothing about the response shape, how the five input modes (csv/json/text/file/structured arrays) interact, or what happens with cycles, self-ownership, or duplicate edges.

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 core operation, then the non-fabrication guarantee, then price and transport. Every sentence carries information and nothing is padded. The endpoint string and price could arguably be structured metadata rather than prose, but they are still useful inline.

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?

For a tool with 15 parameters, nested objects, multiple alternative input channels, and no output schema, this description is thin. It never explains the difference between passing 'ownership' directly versus csv/json/text/file payloads, nor what the returned chains look like, which is the single most important thing an agent needs to plan a call.

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, and the description only gestures at the ownership edge concept, which maps loosely to the 'ownership' array (parentId/childId/percent). The other 14 parameters — csv, json, text, file, companies, directors, exclusions, relationships, sanctionsEntries, enforcementRecords, previousSanctionsEntries, nameVariants, asOf, fetchOfac — get no mention at all, not even which input channel to prefer.

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 concrete verb and resource: it walks supplied parent-child ownership edges into chains. The word 'supplied' usefully signals this is a transform over caller-provided data rather than a lookup. It does not name or distinguish itself from siblings like network-relationship-analyze, which could plausibly cover similar graph ground.

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?

The phrase 'walk supplied parent-child ownership edges' implies the caller must pass ownership data, but there is no explicit when-to-use, no when-not, and no named alternative among the nine siblings. An agent cannot tell from this text whether to reach for this tool or network-relationship-analyze for a graph task.

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