Skip to main content
Glama
Gonzih

mcp-opencorporates

by Gonzih

get_company_officers

Retrieve all current and historical officers of a company, including their positions and service dates, by providing jurisdiction code and company number.

Instructions

Get all officers for a specific company. Returns current and historical officers with positions and dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jurisdiction_codeYesJurisdiction code (e.g. 'us_de', 'gb', 'de')
company_numberYesCompany registration number
pageNoPage number for pagination (default 1)

Implementation Reference

  • TypeScript interface defining input arguments for get_company_officers: jurisdiction_code (string), company_number (string), and optional page (number).
    interface GetCompanyOfficersArgs {
      jurisdiction_code: string;
      company_number: string;
      page?: number;
    }
  • src/index.ts:149-168 (registration)
    Tool registration/definition in the ListToolsRequestSchema handler, including the name 'get_company_officers', description, and input JSON schema.
    {
      name: "get_company_officers",
      description:
        "Get all officers for a specific company. Returns current and historical officers with positions and dates.",
      inputSchema: {
        type: "object",
        properties: {
          jurisdiction_code: {
            type: "string",
            description: "Jurisdiction code (e.g. 'us_de', 'gb', 'de')",
          },
          company_number: {
            type: "string",
            description: "Company registration number",
          },
          page: { type: "number", description: "Page number for pagination (default 1)" },
        },
        required: ["jurisdiction_code", "company_number"],
      },
    },
  • Handler implementation: extracts args, validates required fields, calls the OpenCorporates API at /companies/{jurisdiction_code}/{company_number}/officers, maps officer data to output, and returns results as JSON text.
    case "get_company_officers": {
      const { jurisdiction_code, company_number, page } = args as unknown as GetCompanyOfficersArgs;
      if (!jurisdiction_code || !company_number)
        throw new Error("Parameters 'jurisdiction_code' and 'company_number' are required");
    
      const data = (await apiFetch(
        `/companies/${jurisdiction_code}/${encodeURIComponent(company_number)}/officers`,
        { page }
      )) as { results: { officers: Array<{ officer: Record<string, unknown> }> } };
    
      const officers = data.results?.officers ?? [];
      if (officers.length === 0) return textResult("No officers found for this company.");
    
      const out = officers.map(({ officer: o }) => ({
        name: o["name"],
        position: o["position"],
        uid: o["uid"],
        start_date: o["start_date"],
        end_date: o["end_date"],
        inactive: o["inactive"],
        nationality: o["nationality"],
        occupation: o["occupation"],
        opencorporates_url: o["opencorporates_url"],
      }));
      return textResult(JSON.stringify(out, null, 2));
    }
Behavior3/5

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

With no annotations, the description carries full burden. It states that it returns current and historical officers with positions and dates, indicating a read operation. However, it does not mention pagination behavior, rate limits, or prerequisites beyond the required parameters.

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 a single sentence that efficiently conveys the tool's purpose and return content, with no unnecessary words.

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 simple input (3 parameters) and no output schema, the description covers the main return content (current and historical officers with positions and dates). It lacks details on pagination handling, which is relevant given the 'page' parameter.

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 baseline is 3. The description adds no parameter-specific details beyond what the schema already provides.

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 gets all officers for a specific company. This distinguishes it from siblings like 'search_officers' (which searches across companies) and 'get_company' (which gets company details).

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 implies usage context: for a specific company using jurisdiction and company number. However, it does not explicitly exclude cases or compare with alternatives like 'search_officers' or 'get_company_filings'.

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/Gonzih/mcp-opencorporates'

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