Skip to main content
Glama

UK Due Diligence

by io.github.paulieb89

Search Disqualified Directors

disqualified_search
Read-onlyIdempotent

Check whether a named individual is banned from acting as a UK company director.

Use this tool when asked to check disqualified, banned, or barred directors. Query must be an individual's name (e.g. "Richard Howson") — NOT a company name, which always returns zero results.

Returns names, dates of birth, disqualification period snippets, and officer IDs that can be used with disqualified_profile for full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoAlias for query — the person's name.
queryNoPerson's name to search for, e.g. query='Richard Howson'. NOT a company name.
start_indexNoPagination offset (0-based). Default 0.
items_per_pageNoResults per page (max 100). Default 20.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoMatching disqualified officer records.
queryYesSearch query applied.
has_moreYesTrue if more items may exist beyond this page. Re-call with start_index=start_index+items_per_page to continue.
returnedYesItems actually returned on this page.
start_indexYesPagination offset for this page.
total_resultsYesTotal matching records upstream at Companies House.
items_per_pageYesPage size requested.

Schema Changelog

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

  1. Changed8 schema fields changed
    • addedInput schema / properties / name
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 2,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Alias for query — the person's name."
+}
    • addedInput schema / properties / query / anyOf
      Added value: +[
+  {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / query / default
      Added value: +null
    • changedInput schema / properties / query / description
      Previous value: -"Name of the person to search for"New value: +"Person's name to search for, e.g. query='Richard Howson'. NOT a company name."
    • removedInput schema / properties / query / maxLength
      Removed value: -200
    • removedInput schema / properties / query / minLength
      Removed value: -2
    • removedInput schema / properties / query / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
-  "query"
-]
  2. Added
  3. Removed
  4. Changed15 schema fields changed
    • changedInput schema / properties / items_per_page / description
      Previous value: -"Results per page (max 100)"New value: +"Results per page (max 100). Default 20."
    • removedInput schema / properties / response_format
      Removed value: -{
-  "default": "markdown",
-  "description": "Output format: 'markdown' or 'json'",
-  "type": "string"
-}
    • changedInput schema / properties / start_index / description
      Previous value: -"Pagination offset (0-based)"New value: +"Pagination offset (0-based). Default 0."
    • addedInput schema / properties / start_index / maximum
      Added value: +10000
    • changedOutput schema / description
      Previous value: -"Generic wrapper for non-object return types."New value: +"Paginated disqualified officers search result."
    • addedOutput schema / properties / has_more
      Added value: +{
+  "description": "True if more items may exist beyond this page. Re-call with start_index=start_index+items_per_page to continue.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / items
      Added value: +{
+  "description": "Matching disqualified officer records.",
+  "items": {
+    "description": "A single hit in a disqualified officers search.",
+    "properties": {
+      "address": {
+        "additionalProperties": true,
+        "description": "Last known address of the disqualified officer.",
+        "type": "object"
+      },
+      "date_of_birth": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Date of birth as returned by the search API."
+      },
+      "links": {
+        "additionalProperties": true,
+        "description": "Upstream relational links (self, etc.).",
+        "type": "object"
+      },
+      "officer_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Companies House officer ID extracted from the self link. Pass to disqualified_profile for the full disqualification record."
+      },
+      "snippet": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Upstream match snippet highlighting query terms."
+      },
+      "title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Display title (typically the officer's name)."
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / items_per_page
      Added value: +{
+  "description": "Page size requested.",
+  "type": "integer"
+}
    • addedOutput schema / properties / query
      Added value: +{
+  "description": "Search query applied.",
+  "type": "string"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / returned
      Added value: +{
+  "description": "Items actually returned on this page.",
+  "type": "integer"
+}
    • addedOutput schema / properties / start_index
      Added value: +{
+  "description": "Pagination offset for this page.",
+  "type": "integer"
+}
    • addedOutput schema / properties / total_results
      Added value: +{
+  "description": "Total matching records upstream at Companies House.",
+  "type": "integer"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "query",
+  "total_results",
+  "start_index",
+  "items_per_page",
+  "returned",
+  "has_more"
+]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds key behavioral context beyond that: the company name query returns zero results (a known pitfall), and it reveals the return shape (names, DOBs, snippets, officer IDs) plus a pointer to disqualified_profile for follow-up. This exceeds the annotation baseline without being exhaustive about rate limits or matching nuances.

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?

Four sentences, each earning its place: purpose, when-to-use, critical restriction, and return value summary. Front-loaded with the most important info, no redundancy or fluff. Perfectly sized for quick parsing by an agent.

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?

The tool is simple, has an output schema, and annotations cover safety. The description covers purpose, usage guidelines, a key anti-pattern, and a related-tool pointer. Pagination and limits are already captured in the schema, so nothing critical is missing. The context is complete for reliable invocation.

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%: each parameter has a meaningful description, including the alias relationship between 'name' and 'query' and clarifying 'NOT a company name.' The tool description reinforces this but doesn't introduce new parameter-level semantics. Baseline 3 is appropriate because the schema carries the burden.

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 opens with a specific verb+resource: 'Check whether a named individual is banned from acting as a UK company director.' This clearly distinguishes the tool from siblings like company_search (which searches companies) and disqualified_profile (which retrieves full details for an identified officer). The scope is precise and unambiguous.

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?

Provides explicit when-to-use guidance: 'Use this tool when asked to check disqualified, banned, or barred directors.' It also warns against a common mistake: 'Query must be an individual's name — NOT a company name, which always returns zero results.' This exclusion is valuable and no other tool is suggested for this purpose, making the guidance direct and actionable.

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