Skip to main content
Glama

UK Due Diligence

by io.github.paulieb89

Get Disqualified Director Profile

disqualified_profile
Read-onlyIdempotent

Fetch the full disqualification record for a director by officer ID.

Returns all disqualification orders: reason, Act/section cited, disqualification period, and associated company names. Use disqualified_search first to find the officer ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
officer_idYesCompanies House officer ID. Returned by disqualified_search.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOfficer name.
surnameNoFamily name, if split upstream.
forenameNoGiven name, if split upstream.
officer_idYesCompanies House officer ID looked up.
nationalityNoDeclared nationality.
officer_kindYesWhich CH endpoint returned the record: 'natural' (individual) or 'corporate' (legal entity).
date_of_birthNoDate of birth on record.
disqualificationsNoAll disqualification orders attached to this officer.

Schema Changelog

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

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • changedOutput schema / properties / disqualifications / items / properties / company_names / description
      Previous value: -"Companies associated with this disqualification. The list may be truncated per the `max_companies` input."New value: +"Companies associated with this disqualification. The list may be truncated to 20 entries."
  4. Added
  5. Removed
  6. Changed14 schema fields changed
    • addedInput schema / properties / max_companies
      Added value: +{
+  "default": 20,
+  "description": "Per-order cap on the `company_names[]` array. Prolific disqualified directors are attached to 20+ companies per order. Default 20.",
+  "maximum": 500,
+  "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: +"Full disqualification record for a disqualified officer."
    • addedOutput schema / properties / date_of_birth
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Date of birth on record."
+}
    • addedOutput schema / properties / disqualifications
      Added value: +{
+  "description": "All disqualification orders attached to this officer.",
+  "items": {
+    "description": "A single disqualification order attached to a disqualified director.",
+    "properties": {
+      "address": {
+        "additionalProperties": true,
+        "description": "Address on record at the time of the order.",
+        "type": "object"
+      },
+      "case_identifier": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Upstream case_identifier, when provided."
+      },
+      "company_names": {
+        "description": "Companies associated with this disqualification. The list may be truncated per the `max_companies` input.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "company_names_total": {
+        "default": 0,
+        "description": "Total number of companies originally attached to this order before truncation (may equal `len(company_names)`).",
+        "type": "integer"
+      },
+      "company_names_truncated": {
+        "default": false,
+        "description": "True if the company_names list was truncated to max_companies.",
+        "type": "boolean"
+      },
+      "disqualified_from": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Start date of the disqualification period."
+      },
+      "disqualified_until": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "End date of the disqualification period."
+      },
+      "heard_on": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Date the order was heard, when provided."
+      },
+      "last_variation": {
+        "additionalProperties": true,
+        "description": "Details of the last variation of this order, if any.",
+        "type": "object"
+      },
+      "reason": {
+        "additionalProperties": true,
+        "description": "Reason block as returned upstream: act, section, description_identifier, article, etc.",
+        "type": "object"
+      },
+      "undertaken_on": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Date the undertaking was given, when provided."
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / forename
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Given name, if split upstream."
+}
    • addedOutput schema / properties / name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Officer name."
+}
    • addedOutput schema / properties / nationality
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Declared nationality."
+}
    • addedOutput schema / properties / officer_id
      Added value: +{
+  "description": "Companies House officer ID looked up.",
+  "type": "string"
+}
    • addedOutput schema / properties / officer_kind
      Added value: +{
+  "description": "Which CH endpoint returned the record: 'natural' (individual) or 'corporate' (legal entity).",
+  "type": "string"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / surname
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Family name, if split upstream."
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "officer_id",
+  "officer_kind"
+]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  7. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds the return contents (reasons, Act/section, period, company names) and reinforces the need for a pre-discovered officer ID, which is valuable context beyond the annotations.

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 two sentences: a clear action statement and a compact list of returns plus usage note. Every phrase contributes value with no redundancy.

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 a single parameter with 100% schema coverage and an output schema present, the description fully captures the tool's purpose, prerequisites, and return contents. It is sufficiently complete for an agent to invoke correctly.

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?

The schema already covers officer_id with a full description including its source. The description repeats this linkage but does not introduce new parameter constraints or types, so the baseline of 3 is appropriate.

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 identifies the action ('Fetch') and the resource ('full disqualification record for a director') via officer ID. It distinguishes itself from the sibling disqualified_search by focusing on retrieval of a specific record rather than searching.

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

Usage Guidelines5/5

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

It explicitly states the prerequisite workflow: 'Use disqualified_search first to find the officer ID.' This provides clear guidance on when to use this tool and points to the alternative tool for discovery.

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