Skip to main content
Glama

UK Due Diligence

by io.github.paulieb89

Search Companies House

company_search
Read-onlyIdempotent

Search the Companies House register by company name or keyword.

Returns a paginated list of matching companies with name, number, status, SIC codes, incorporation date, and registered address. Use company_profile for the full record once you have the company number. Re-call with start_index=start_index+items_per_page to fetch the next page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesCompany name or keyword to search for
start_indexNoPagination offset. Default 0.
company_typeNoFilter by company type (e.g. 'ltd', 'llp'). Omit to search all.
company_statusNoFilter by company status (e.g. 'active', 'dissolved'). Omit to search all.
items_per_pageNoNumber of results to return (max 100). Default 20.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoMatching companies. Use the `company_number` field to call company_profile, company_officers, or company_psc for full detail.
queryYesThe query string that was searched.
has_moreYesTrue if more results exist beyond this page. Re-call with start_index=start_index+items_per_page to fetch the next page.
returnedYesNumber of items actually returned on this page.
start_indexYesNumber of results skipped before this page (upstream start_index).
total_resultsYesTotal matching companies in Companies House (server-side).
items_per_pageYesPage size requested from the API for this call.

Schema Changelog

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

  1. Added
  2. Removed
  3. Changed15 schema fields changed
    • changedInput schema / properties / items_per_page / description
      Previous value: -"Number of results to return (max 100)"New value: +"Number of results to return (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"New value: +"Pagination offset. 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 result of a Companies House company search."
    • addedOutput schema / properties / has_more
      Added value: +{
+  "description": "True if more results exist beyond this page. Re-call with start_index=start_index+items_per_page to fetch the next page.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / items
      Added value: +{
+  "description": "Matching companies. Use the `company_number` field to call company_profile, company_officers, or company_psc for full detail.",
+  "items": {
+    "description": "A single entry in a Companies House search result.",
+    "properties": {
+      "address": {
+        "additionalProperties": true,
+        "description": "Registered office address as returned by the Companies House API.",
+        "type": "object"
+      },
+      "company_number": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Companies House company number (e.g. '12345678')."
+      },
+      "company_status": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Company status (e.g. 'active', 'dissolved', 'liquidation')."
+      },
+      "company_type": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Companies House company type code (e.g. 'ltd', 'plc', 'llp')."
+      },
+      "date_of_creation": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Incorporation date in ISO format (YYYY-MM-DD)."
+      },
+      "description": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Short upstream description (usually number + status + creation date)."
+      },
+      "sic_codes": {
+        "description": "Standard Industrial Classification codes associated with the company.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Registered company name."
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / items_per_page
      Added value: +{
+  "description": "Page size requested from the API for this call.",
+  "type": "integer"
+}
    • addedOutput schema / properties / query
      Added value: +{
+  "description": "The query string that was searched.",
+  "type": "string"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / returned
      Added value: +{
+  "description": "Number of items actually returned on this page.",
+  "type": "integer"
+}
    • addedOutput schema / properties / start_index
      Added value: +{
+  "description": "Number of results skipped before this page (upstream start_index).",
+  "type": "integer"
+}
    • addedOutput schema / properties / total_results
      Added value: +{
+  "description": "Total matching companies in Companies House (server-side).",
+  "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
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds behavioral details beyond annotations: it returns a paginated list with specific fields (name, number, status, SIC codes, incorporation date, registered address) and explains the pagination mechanism, which is valuable, non-obvious context.

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 three sentences, each earning its place: purpose, return behavior, and referral/pagination guidance. It is front-loaded and free of 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 the tool's search nature, the description covers essential aspects: what it searches, what it returns, how pagination works, and when to use a sibling tool (company_profile). The output schema presumably handles return structure details, so the description is complete.

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 coverage is 100%, so baseline is 3. The description enriches this by clarifying 'query' as company name or keyword and by explicitly stating the pagination formula (start_index=start_index+items_per_page), which adds meaning beyond the schema's individual parameter descriptions.

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 it searches the Companies House register by company name or keyword, with a specific verb and resource. It also distinguishes itself from company_profile by explicitly directing users there for full records, making its scope 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?

The description explicitly names an alternative (company_profile) and provides an exclusion ('Use company_profile for the full record once you have the company number'). It also gives concrete pagination instructions (re-call with start_index+items_per_page), giving clear when-to-use guidance.

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