Skip to main content
Glama

UK Due Diligence

by io.github.paulieb89

Get Company Officers

company_officers
Read-onlyIdempotent

Fetch officers for a Companies House company number.

Returns directors, secretaries, and other officers with appointment dates, nationality, and country of residence. Resigned officers are excluded by default; set include_resigned=true for historical DD. Pagination is handled internally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_indexNoIgnored — pagination is handled internally. Only accepted to avoid call failures.
company_numberYesCompanies House company number (8 digits, e.g. '03782379'). Returned by company_search.
items_per_pageNoIgnored — pagination is handled internally. Only accepted to avoid call failures.
include_resignedNoInclude resigned/historic officers. Default false for backwards-compatible current-officer queries.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal officers returned (filtered by include_resigned).
officersNoOfficer records.
company_numberYesCompanies House company number.
include_resignedYesWhether resigned officers were included in this result.
high_appointment_count_flagNoNumber of active officers with 10+ total appointments, or null if appointment counts were not fetched. Non-zero values are a nominee/phoenix director risk signal.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedInput schema / properties / include_resigned
      Added value: +{
+  "default": false,
+  "description": "Include resigned/historic officers. Default false for backwards-compatible current-officer queries.",
+  "type": "boolean"
+}
    • changedInput schema / properties / start_index / description
      Previous value: -"Ignored — all officers are returned in one call."New value: +"Ignored — pagination is handled internally. Only accepted to avoid call failures."
    • addedOutput schema / properties / officers / items / properties / officer_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Companies House officer ID, extracted from links.officer.appointments. Pass to officer_appointments to discover this person's full appointment history across companies, including dissolved or insolvent ones."
+}
  2. Added
  3. Removed
  4. Changed2 schema fields changed
    • addedInput schema / properties / items_per_page
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Ignored — pagination is handled internally. Only accepted to avoid call failures."
+}
    • addedInput schema / properties / start_index
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Ignored — all officers are returned in one call."
+}
  5. Added
  6. Removed
  7. Changed11 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "description": "Max officers to fetch from Companies House (upstream items_per_page). Default 100.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / response_format
      Removed value: -{
-  "default": "markdown",
-  "description": "Output format: 'markdown' or 'json'",
-  "type": "string"
-}
    • changedOutput schema / description
      Previous value: -"Generic wrapper for non-object return types."New value: +"List of officers for a given company."
    • addedOutput schema / properties / company_number
      Added value: +{
+  "description": "Companies House company number.",
+  "type": "string"
+}
    • addedOutput schema / properties / high_appointment_count_flag
      Added value: +{
+  "default": 0,
+  "description": "Number of active officers with 10+ total appointments. Non-zero values are a nominee/phoenix director risk signal.",
+  "type": "integer"
+}
    • addedOutput schema / properties / include_resigned
      Added value: +{
+  "description": "Whether resigned officers were included in this result.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / officers
      Added value: +{
+  "description": "Officer records.",
+  "items": {
+    "description": "A single officer (director, secretary, etc.) of a company.",
+    "properties": {
+      "address": {
+        "additionalProperties": true,
+        "description": "Officer correspondence address.",
+        "type": "object"
+      },
+      "appointed_on": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Date of appointment (ISO YYYY-MM-DD)."
+      },
+      "appointment_count": {
+        "default": 0,
+        "description": "Total number of other active appointments held by this officer. Values of 10+ are a nominee/phoenix risk signal.",
+        "type": "integer"
+      },
+      "country_of_residence": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Declared country of residence."
+      },
+      "date_of_birth": {
+        "additionalProperties": true,
+        "description": "Partial date of birth (month/year) as returned by CH.",
+        "type": "object"
+      },
+      "links": {
+        "additionalProperties": true,
+        "description": "Upstream relational links (e.g. officer profile URL).",
+        "type": "object"
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Officer name as recorded at CH."
+      },
+      "nationality": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Declared nationality."
+      },
+      "occupation": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Declared occupation."
+      },
+      "officer_role": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Officer role (e.g. 'director', 'secretary', 'llp-member')."
+      },
+      "resigned_on": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Date of resignation if resigned, otherwise null."
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / total
      Added value: +{
+  "description": "Total officers returned (filtered by include_resigned).",
+  "type": "integer"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "company_number",
+  "include_resigned",
+  "total"
+]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  8. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already communicate read-only, idempotent, safe behavior. The description adds meaningful context beyond that: resigned officers are excluded by default, include_resigned=true opts into historical data, and pagination is handled internally.

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 short, front-loaded with the core purpose, and every sentence adds information. It covers behavior, output content, and the key parameter option without verbosity.

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?

Given the rich schema, output schema, and annotation coverage, the description completes the picture with the important defaults and automatic pagination. A caller has enough context to invoke it correctly.

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 description coverage is 100%, so the parameters are already well documented. The description adds useful framing around include_resigned and pagination, reinforcing the schema without introducing ambiguity.

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 states a specific action and resource: 'Fetch officers for a Companies House company number.' It also names the officer categories returned, which distinguishes this from sibling tools like company_profile or company_charges.

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 gives clear usage context: who is returned by default, how to include resigned officers, and that pagination is automatic. It does not explicitly name an alternative tool, but handles the main operational decisions a caller needs to make.

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

All UK Due Diligence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

The domain-specific tools are clearly distinct (search vs profile for each register), and the generic search/fetch tools are designed to route across them. Potential overlap between company_officers and company_psc is resolved by clear descriptions of officers vs beneficial ownership. Slight ambiguity exists between generic fetch/search and the domain-specific counterparts, but the routing logic is well-documented.

Naming Consistency4/5

Most tools follow a consistent resource_action pattern with clear prefixes (charity_, company_, disqualified_, gazette_). Exceptions like company_officers, company_psc, sanctions_screen, and vat_validate deviate from the verb-first convention, and generic tools (fetch, search, get_prompt, list_prompts) do not follow the pattern. Overall, the naming is readable and predictable despite a few outliers.

Tool Count4/5

With 17 tools, the server sits slightly above the typical 3-15 well-scoped range, but the breadth of the domain (Companies House, Charity Commission, disqualifications, Gazette insolvency, sanctions, land registry, VAT) justifies the count. Each tool serves a distinct data source or action, and the two prompt-management tools are standard MCP utilities. The count feels appropriate rather than excessive.

Completeness4/5

The server covers the core due diligence workflow: searching and retrieving profiles for companies, charities, and disqualified directors, plus insolvency notices, sanctions screening, land transactions, and VAT validation. Minor gaps exist, such as no direct tool for company accounts or court judgments, but these are not core to the apparent purpose and can be worked around.

Resources