Skip to main content
Glama
vdmeu

RegistrumMCP

Get director network

get_network

Map corporate networks by identifying companies connected through shared directors. Analyze group structures and related party relationships for UK companies.

Instructions

Map the corporate network connected to a UK company via shared directors. Returns all companies connected through shared board members, up to the specified depth. Each connected company includes its name, number, status, and the directors it shares with the focal company. Useful for identifying corporate group structures, related party relationships, and director interlocks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_numberYesCompanies House company number, e.g. '00445790' for Tesco PLC
depthNoTraversal depth: 1 = direct connections only, 2 = connections of connections (default 1). Depth 2 can return many results for large companies.

Implementation Reference

  • The handler function for get_network tool. Takes company_number and optional depth parameter, constructs API path, calls the registrum API endpoint /company/{company_number}/network, and returns the network data or error.
    async ({ company_number, depth }) => {
      try {
        const params = depth ? `?depth=${depth}` : "";
        const data = await api(`/company/${company_number}/network${params}`);
        return text(data);
      } catch (e) {
        return err(String(e));
      }
    }
  • Input schema for get_network tool defining two parameters: company_number (required, must match UK company number format) and depth (optional, 1-2 integer for network traversal depth).
    inputSchema: {
      company_number: z
        .string()
        .regex(/^[A-Z0-9]{1,8}$/)
        .describe("Companies House company number, e.g. '00445790' for Tesco PLC"),
      depth: z
        .number()
        .int()
        .min(1)
        .max(2)
        .optional()
        .describe(
          "Traversal depth: 1 = direct connections only, 2 = connections of connections (default 1). " +
          "Depth 2 can return many results for large companies."
        ),
  • src/server.ts:174-210 (registration)
    Complete registration of get_network tool with MCP server, including metadata (title, description), input schema, and handler function.
    server.registerTool(
      "get_network",
      {
        title: "Get director network",
        description:
          "Map the corporate network connected to a UK company via shared directors. " +
          "Returns all companies connected through shared board members, up to the specified " +
          "depth. Each connected company includes its name, number, status, and the directors " +
          "it shares with the focal company. Useful for identifying corporate group structures, " +
          "related party relationships, and director interlocks.",
        inputSchema: {
          company_number: z
            .string()
            .regex(/^[A-Z0-9]{1,8}$/)
            .describe("Companies House company number, e.g. '00445790' for Tesco PLC"),
          depth: z
            .number()
            .int()
            .min(1)
            .max(2)
            .optional()
            .describe(
              "Traversal depth: 1 = direct connections only, 2 = connections of connections (default 1). " +
              "Depth 2 can return many results for large companies."
            ),
        },
      },
      async ({ company_number, depth }) => {
        try {
          const params = depth ? `?depth=${depth}` : "";
          const data = await api(`/company/${company_number}/network${params}`);
          return text(data);
        } catch (e) {
          return err(String(e));
        }
      }
    );
  • Helper function that performs HTTP fetch to registrum API with API key authentication. Used by get_network handler to fetch company network data.
    export async function callApi(
      path: string,
      apiKey: string,
      baseUrl: string = API_BASE
    ): Promise<unknown> {
      if (!apiKey) {
        throw new Error(
          "REGISTRUM_API_KEY is not set. Get a free key at https://registrum.co.uk and set it in your MCP client config."
        );
      }
      const res = await fetch(`${baseUrl}${path}`, {
        headers: { "X-API-Key": apiKey },
      });
      if (!res.ok) {
        const body = await res.text();
        throw new Error(`API error ${res.status}: ${body}`);
      }
      return res.json();
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: the tool returns all connected companies up to specified depth, includes specific fields for each company, and mentions that depth 2 'can return many results for large companies.' However, it doesn't cover rate limits, authentication needs, or potential performance implications beyond the depth warning.

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?

The description is efficiently structured in three sentences: first states purpose and scope, second describes output format, third provides usage context. Every sentence adds value with zero waste. It's appropriately sized and front-loaded with the core functionality.

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?

Given the tool's moderate complexity (network traversal), no annotations, and no output schema, the description does well but has gaps. It explains what the tool does, when to use it, and output format at a high level, but doesn't detail the exact structure of returned data or potential limitations beyond depth considerations. For a network analysis tool without output schema, more detail on result format would be helpful.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already fully documents both parameters. The description adds marginal value by mentioning 'up to the specified depth' and the traversal concept, but doesn't provide additional syntax or format details beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the tool's purpose: mapping corporate networks via shared directors for UK companies. It specifies the verb ('Map'), resource ('corporate network'), scope ('connected to a UK company via shared directors'), and distinguishes from siblings like get_company (single company) or get_directors (directors of one company).

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?

The description provides clear context for when to use this tool: 'identifying corporate group structures, related party relationships, and director interlocks.' It doesn't explicitly state when not to use it or name alternatives among siblings, but the context strongly implies this is for network analysis rather than retrieving individual company or director data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vdmeu/registrum-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server