Skip to main content
Glama

A company's identified sole-shareholder network

company_group
Read-onlyIdempotent

Get a company's sole-shareholder network from links with no ending identified in available BORME publications. Links do not establish current ownership, control or a legal group. Use it for identified sole shareholders or connected companies; use group_history for events. Name lookup: multiple matches return {ambiguous: true, candidates}; none return {error, suggested_companies}.

Returns {company_slug, parents (nearest first), top_parent_slug, members: [{slug, name, province, status, owner_slug, depth, link_kind, since, evidence: {event_id, date, text (excerpt, max 600 chars)}}], unresolved, truncated, note}. The highest member has owner_slug, link_kind, since and evidence null. Names not matched to exactly one company appear as printed in unresolved; do not treat them as resolved companies. Max 200 members. include_directors adds director links, not members. Empty parents does not rule out control or a legal group.

Read-only. Pro plan; X-API-Key header.

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": {
      "company": "<company>"
    },
    "name": "company_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany slug, e.g. vaz-metales-sl (from search_companies), or a name of at least 3 letters or digits, e.g. "Mercadona".
include_directorsNoOptional, one of true or false (default false), e.g. true to add legal persons appointed as directors of members and the companies a member administers, marked as director links; a director link alone does not make a company a member of the group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is largely covered. The description adds genuinely useful behavioral context beyond that: the max 200 member cap, the ambiguity/error return paths for name lookup, unresolved names, the truncated flag, and the Pro plan plus X-API-Key auth requirement. The disclaimer that links do not establish current ownership or legal group status is the strongest addition, since it prevents misreading the result as a control assertion.

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?

Front-loaded with the core operation, then routing, then return shape and caveats. Dense but nearly every sentence carries information; the return-shape block is long but substitutes for a missing output schema, so it earns its space. Minor redundancy with the schema on include_directors keeps it from a 5.

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

Completeness5/5

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

With no output schema, the description fully specifies the return object including per-member fields, null semantics for the top member, the evidence excerpt cap, unresolved handling, truncation, and the 200-member limit. It also covers name-resolution failure modes and the auth/plan requirement, so an agent has everything needed to call and correctly interpret this tool.

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 coverage is 100% and both parameters are fully documented in the input schema, including slug-vs-name formats and the director-link caveat. The description repeats the include_directors meaning almost verbatim from the schema and adds only the name-lookup ambiguity behavior ({ambiguous: true, candidates} / {error, suggested_companies}), which is return behavior rather than new parameter semantics. This leaves the description adding little meaning beyond what the structured fields already provide.

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?

The description opens with a specific verb and resource: "Get a company's sole-shareholder network from links with no ending identified in available BORME publications." It also states the scope limit (identified sole shareholders, not control or legal group), which distinguishes it from general ownership tools and from the explicitly named sibling group_history.

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?

Explicit routing: "Use it for identified sole shareholders or connected companies; use group_history for events." It also states an exclusion for the include_directors flag ("adds director links, not members") and warns that empty parents does not rule out control, so an agent knows both when to call it and how not to over-read the result.

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.