Skip to main content
Glama

Relationships between companies, investors and people

get_relationships
Read-only

Returns the filed relationships around a company, an investment house or a person, private companies included (Anthropic, OpenAI): owns, invests_in, insider_of, holds_rights_in, customer_of, agreement_with, acquired, lends_to: each with the filings that prove it. depth: 2 adds the neighbours' relationships; notes in the answer says how to read each field. Use it when the user asks how companies are connected, who is behind a company, its customers, suppliers or lenders, or what links two of them. For a full shareholder list, use get_ownership; for one investor's portfolio, get_holders.

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": {
      "center": "<center>"
    },
    "name": "get_relationships"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoWhich relationships (default 'all'): capital (owns, invests_in, holds_rights_in), value_chain (customer_of, agreement_with, acquired, lends_to: who buys, sells, merges with and lends to whom), governance (insider_of), competition (competes_with).
depthNo1 (default): the center's relationships; 2: its neighbours' too.
limitNoHow many relationships at most (default 40, max 200).
sinceNoOnly relationships whose proving filing is dated on or after this day (YYYY-MM-DD).
centerYesThe company, house or person at the center: a ticker, a company name (listed or not: 'Anthropic'), a holder's key or name ('vanguard', 'Elon Musk'), or a typed id from a previous answer (company:nvda, holder:vanguard, person:<id>, gov:us).
statusNo'active' (default): relationships the filings still state, a customer the supplier's latest report still names, a contract not past its stated term; 'all': past ones too, each with its relationshipStatus (not_restated, expired).
naturesNoComma-separated natures within the view: owns, invests_in, holds_rights_in, insider_of, customer_of, agreement_with, acquired, lends_to. supplier_of and competes_with are declared but have no source yet: a company's suppliers are the `to` end of customer_of relationships whose `from` is that company.
minShareNoMinimum share of capital, as a fraction (0.01 = 1%), for ownership relationships.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / status / description
      Previous value: -"'active' (default): relationships the filings still state — a customer the supplier's latest report still names, a contract not past its stated term; 'all': past ones too, each with its relationshipStatus (not_restated, expired)."New value: +"'active' (default): relationships the filings still state, a customer the supplier's latest report still names, a contract not past its stated term; 'all': past ones too, each with its relationshipStatus (not_restated, expired)."
  2. Changed2 schema fields changed
    • changedInput schema / properties / natures / description
      Previous value: -"Comma-separated natures within the view: owns, invests_in, holds_rights_in, insider_of, customer_of, supplier_of, agreement_with, acquired, competes_with, lends_to."New value: +"Comma-separated natures within the view: owns, invests_in, holds_rights_in, insider_of, customer_of, agreement_with, acquired, lends_to. supplier_of and competes_with are declared but have no source yet: a company's suppliers are the `to` end of customer_of relationships whose `from` is that company."
    • changedInput schema / properties / view / description
      Previous value: -"Which relationships (default 'all')."New value: +"Which relationships (default 'all'): capital (owns, invests_in, holds_rights_in), value_chain (customer_of, agreement_with, acquired, lends_to: who buys, sells, merges with and lends to whom), governance (insider_of), competition (competes_with)."
  3. Changed4 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / minShare / maximum
      Added value: +1
    • addedInput schema / properties / minShare / minimum
      Added value: +0
  4. Changed1 schema field changed
    • changedInput schema / properties / status / description
      Previous value: -"'active' (default): relationships the filings still state — a customer the supplier's latest report still names, a contract still restated and not past its stated term; 'all': past ones too, each with its relationshipStatus (not_restated, expired)."New value: +"'active' (default): relationships the filings still state — a customer the supplier's latest report still names, a contract not past its stated term; 'all': past ones too, each with its relationshipStatus (not_restated, expired)."
  5. Changed1 schema field changed
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "'active' (default): relationships the filings still state — a customer the supplier's latest report still names, a contract still restated and not past its stated term; 'all': past ones too, each with its relationshipStatus (not_restated, expired).",
      +  "enum": [
      +    "active",
      +    "all"
      +  ],
      +  "type": "string"
      +}
  6. Added

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds real value by noting that every relationship carries its proving filings and that the response includes a `notes` field explaining how to read each field. Beyond that it says nothing about result shape, pagination behavior at the 200 cap, or ordering — modest additions against an already-informative annotation set.

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?

One dense paragraph, front-loaded with purpose, then narrowing to usage and alternatives — no filler sentences. It is on the longer side and packs enum names into the purpose sentence, but every clause carries routing or scope information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters, no output schema, and a graph-shaped result, the description does enough: it names the relationship vocabulary, discloses private-company coverage, explains depth expansion and the self-describing `notes` field. It stops short of describing result structure (edge objects, from/to orientation) which matters for a graph tool with no output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description goes slightly beyond it: it highlights the `depth: 2` neighbour-expansion behavior and the `notes` interpretation aid, and ties filtering to proving filings. It still repeats rather than extends the enum semantics for view/natures/status, keeping it out of 5 territory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (returns filed relationships around a company, investment house or person) and enumerates the exact relationship types returned. It also carves out scope against siblings (get_ownership, get_holders), so an agent can distinguish it from the 18 other tools without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger list ('how companies are connected, who is behind a company, its customers, suppliers or lenders, or what links two of them') and names two concrete alternatives with the condition that selects each ('full shareholder list -> get_ownership; one investor's portfolio -> get_holders').

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.