Skip to main content
Glama
vdmeu

RegistrumMCP

Get company directors

get_directors

Retrieve current and past directors for UK companies, including appointment dates, roles, and their corporate history across multiple organizations.

Instructions

Get the current and past directors for a UK company, including each director's name, role, appointment date, resignation date (if applicable), nationality, country of residence, and a list of other companies they serve or have served as director. This gives you a full picture of a director's corporate history in one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_numberYesCompanies House company number, e.g. '00445790' for Tesco PLC

Implementation Reference

  • The handler function for get_directors tool - an async function that takes company_number, calls the API endpoint /company/{company_number}/directors, and returns the formatted response or error.
    async ({ company_number }) => {
      try {
        const data = await api(`/company/${company_number}/directors`);
        return text(data);
      } catch (e) {
        return err(String(e));
      }
    }
  • Input schema for get_directors tool using Zod - validates company_number as a string matching regex pattern /^[A-Z0-9]{1,8}$/ (Companies House company number format).
    inputSchema: {
      company_number: z
        .string()
        .regex(/^[A-Z0-9]{1,8}$/)
        .describe("Companies House company number, e.g. '00445790' for Tesco PLC"),
    },
  • src/server.ts:148-172 (registration)
    Tool registration for get_directors using server.registerTool() - includes title, description, inputSchema, and the handler function.
    server.registerTool(
      "get_directors",
      {
        title: "Get company directors",
        description:
          "Get the current and past directors for a UK company, including each director's " +
          "name, role, appointment date, resignation date (if applicable), nationality, " +
          "country of residence, and a list of other companies they serve or have served as " +
          "director. This gives you a full picture of a director's corporate history in one call.",
        inputSchema: {
          company_number: z
            .string()
            .regex(/^[A-Z0-9]{1,8}$/)
            .describe("Companies House company number, e.g. '00445790' for Tesco PLC"),
        },
      },
      async ({ company_number }) => {
        try {
          const data = await api(`/company/${company_number}/directors`);
          return text(data);
        } catch (e) {
          return err(String(e));
        }
      }
    );
  • callApi helper function that performs the actual HTTP fetch to the Registrum API with API key authentication - used by get_directors handler via the 'api' wrapper.
    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();
    }
  • Helper functions 'text' and 'err' that format successful and error responses respectively for MCP tool outputs - used by get_directors handler to return results.
    function text(content: unknown) {
      return {
        content: [{ type: "text" as const, text: JSON.stringify(content, null, 2) }],
      };
    }
    
    function err(message: string) {
      return {
        isError: true as const,
        content: [{ type: "text" as const, text: message }],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It describes what data is returned but lacks behavioral details such as whether this is a read-only operation, if it requires authentication, rate limits, error handling, or pagination. The phrase 'in one call' hints at completeness but doesn't clarify limitations.

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 front-loaded with the core purpose in the first sentence, followed by additional context in the second. Every sentence adds value by detailing returned data and benefits, with no wasted words or redundancy.

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

Completeness3/5

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

Given no annotations and no output schema, the description covers the purpose and data scope well but lacks completeness on behavioral aspects like safety, performance, or error handling. For a tool with one parameter and no complex schema, it's adequate but has clear gaps in operational context.

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?

The input schema has 100% description coverage for the single parameter (company_number), so the baseline is 3. The description adds value by specifying this is for 'UK company' and mentioning 'Companies House', which provides context beyond the schema's pattern example, though it doesn't detail parameter usage further.

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 verb 'Get' and the resource 'current and past directors for a UK company', with specific details about the data returned (name, role, dates, nationality, etc.). It distinguishes from sibling tools by focusing on director information rather than company details, financials, networks, or search capabilities.

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

Usage Guidelines3/5

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

The description implies usage when director information is needed for a UK company, but it doesn't explicitly state when to use this tool versus alternatives like get_company or get_network. No exclusions or prerequisites are mentioned, leaving some ambiguity about tool selection.

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