Skip to main content
Glama

BRAINIAC Corporate Ownership, Sanctions & Investigation

Cross-check company identity

corporate-intelligence_company-identity-cross-check

Compare supplied company records by registry number, LEI, and normalized names. Possible matches are never treated as confirmed. Price $0.05 USDC. POST /api/v1/corporate-intelligence/company-identity-cross-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_company-identity-cross-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.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it states that possible matches are never treated as confirmed, discloses the $0.05 USDC price, names the POST endpoint, and warns that unpaid calls return 402 and do not run. What is missing is any indication of what the comparison result contains or how conflicts between registry number, LEI, and names are weighed.

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?

Four short sentences, front-loaded with the purpose, followed by the accuracy caveat, the price, and the payment failure mode. Nothing is padded and each sentence carries distinct information.

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 complex tool: 15 parameters, nested object arrays, no output schema, and no annotations. The description covers the commercial and failure behavior well but leaves the input contract almost entirely unaddressed, which is a substantial gap for an agent trying to assemble a valid request.

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 does not. It mentions registry number, LEI, and names, but says nothing about the csv/json/text/file input alternatives, asOf, fetchOfac, or the directors/ownership/sanctions arrays. An agent has to infer the whole input shape from the tool schema alone.

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 opens with a specific verb and resource: 'Compare supplied company records by registry number, LEI, and normalized names'. That tells an agent exactly what the operation is. It does not explicitly separate itself from close siblings such as name-variant-resolve or registry-record-normalize, 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?

The description states what the tool does but never says when to reach for it over the sibling tools. There is no guidance on prerequisites, input requirements (e.g. that at least two company records are needed to compare), or when a different tool would be the better call.

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