Skip to main content
Glama

Sisoco One

Ownership chain of a UK company

sisoco_ownership_chain
Read-onlyIdempotent

Reads the company's register of persons with significant control (Companies House) and walks owners upwards: who owns or controls it, who owns them, and so on, with cycle protection. Owners above the first level appear when their own register was read before; call again with an owner's company number to extend the chain. Individuals are returned by name only, as published. Cost: 1 lookup (same as GET /v1/companies/uk/{company_number}/ownership-chain).

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_number": "<company_number>"
    },
    "name": "sisoco_ownership_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_depthNoLevels of owners to walk (1–25)
company_numberYesCompanies House number, e.g. 00445790 or SC123456; short numbers are zero-padded

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses cycle protection, the incremental read-again behavior that governs how deep results actually get, that individuals are returned by name only as published, and the cost model (1 lookup, same as the underlying endpoint). These are exactly the traits an agent needs before calling.

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?

Three tight sentences: what it reads and walks, how to extend the chain, then a caveat and cost note. Nothing is repeated and the core operation is front-loaded.

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 an output schema present, the description need not explain return structure, and it still adds the one caveat that matters (individuals by name only). For a two-parameter read-only lookup with full schema coverage, nothing an agent needs in order to call it correctly is missing.

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 company_number and max_depth are already documented, establishing a baseline of 3. The description adds genuine meaning by framing company_number as something you pass an owner's number into in order to extend the chain, which is not evident from the 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 names a specific verb and resource: reading the Companies House register of persons with significant control and walking owners upward. This is concrete enough that an agent can tell it apart from check/search-style siblings, but it never explicitly contrasts itself with any of them, leaving that differentiation to inference.

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

Usage Guidelines4/5

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

It gives real usage context: owners above the first level only appear if their own register was previously read, and the agent should 'call again with an owner's company number to extend the chain.' That is an actionable iteration rule, though there is no explicit statement of when not to use this versus sisoco_check_company or sisoco_search_company.

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