Skip to main content
Glama

BRAINIAC Company Intelligence

Get company ownership

company-intelligence_ownership

Retrieve parent and subsidiary relationships from GLEIF. Price $0.03 USDC. POST /api/v1/company-intelligence/ownership. Unpaid calls return 402 and do not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identifier": "<identifier>"
    },
    "name": "company-intelligence_ownership"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYes

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 does add real behavioral context: it is a paid call ($0.03 USDC) and unpaid requests return 402 without executing, which tells the agent about cost and failure mode. It omits other behavioral facts such as accepted identifier formats, output structure, and any latency or rate constraints.

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?

Three short, front-loaded sentences: purpose, price, endpoint, and payment behavior — no filler. Slightly clipped style, but every sentence carries 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?

No output schema and no annotations, so the description must carry the load, yet it never explains the identifier input or what the ownership relationships look like (names, LEIs, hierarchy depth). For a paid, single-param lookup this leaves a notable gap.

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% for the single parameter 'identifier', and the description never clarifies what it expects (implied LEI given GLEIF, but not stated). The maxLength 30 hint suggests an LEI but that is inference, not documentation, so the description fails to compensate for the schema gap.

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 ('Retrieve parent and subsidiary relationships') plus the data source (GLEIF), which is enough to distinguish it from profile/financials/filings siblings without opening a schema. It stops short of explicitly contrasting itself with them.

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 guidance on when to choose this tool over the sibling lookups, nor on prerequisites (e.g., which identifier types are accepted, LEI vs name). The only situational info is a billing/failure note about unpaid calls.

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