Skip to main content
Glama

BRAINIAC Corporate Ownership, Sanctions & Investigation

Resolve corporate name variants

corporate-intelligence_name-variant-resolve

Group legal, trading, and alias names per company. Similar-only variants stay possible and are not confirmed identity matches. Price $0.04 USDC. POST /api/v1/corporate-intelligence/name-variant-resolve. 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_name-variant-resolve"
  }
}

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 pricing, the unpaid-call 402 failure mode, and an important confidence limitation about non-confirmed matches. However, it does not explain whether the operation mutates data, what permissions are needed, rate limits, or what the response contains.

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?

The description is four compact sentences, front-loads the purpose, then adds the key caveat, price, endpoint, and payment failure behavior. Every sentence carries operational or interpretive value without unnecessary wording.

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 high-complexity tool with 15 parameters, nested objects, no schema descriptions, no output schema, and no annotations, the description is far too thin. It covers purpose and some payment behavior but leaves input formats, required data shapes, and return values essentially unexplained.

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

Parameters1/5

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

The input schema has 15 parameters with 0% schema description coverage, including complex nested arrays and file inputs. The description mentions legal, trading, and alias names only in general terms and provides no guidance on how to use csv, json, text, file, companies, directors, ownership, sanctionsEntries, or the other parameters.

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 states a specific action: grouping legal, trading, and alias names per company. It also clarifies that similar-only variants remain possible and are not confirmed identity matches, which sharpens the tool's purpose. It does not explicitly contrast itself with sibling tools, so it falls 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?

There is no explicit guidance on when to use this tool versus alternatives such as identity cross-checking or registry normalization. The caveat about similar-only variants is useful interpretation guidance but does not tell an agent when this tool is the right choice.

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