Skip to main content
Glama

Companies House

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Companies

search_companies
Read-onlyIdempotent

Search UK Companies House by company name. Returns matches with company number, name, status (active/dissolved), type, registered office address, and incorporation date. Use the company_number to look up officers, filings, and PSCs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesCompany name (full or partial)
start_indexNoPagination offset (default 0)
items_per_pageNo1-100 (default 20)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of companies matching the search query
returnedYesNumber of companies returned in this response
companiesYesList of matching companies

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Apple"
+  },
+  {
+    "items_per_page": 10,
+    "query": "Tesco PLC",
+    "start_index": 0
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "companies": {
+      "description": "List of matching companies",
+      "items": {
+        "properties": {
+          "address": {
+            "description": "Registered office address snippet",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ch_url": {
+            "description": "Link to company profile on Companies House website",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "company_number": {
+            "description": "UK company number",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "incorporated_on": {
+            "description": "Incorporation date (ISO format)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Company name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "Company status (active, dissolved, etc.)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Company type (private limited, public limited, etc.)",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of companies returned in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of companies matching the search query",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "companies"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds value by specifying return fields and pagination defaults (implicit from schema examples), confirming no destructive behavior.

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: the first states core functionality and return fields, the second guides subsequent actions. No redundant information; efficient and front-loaded.

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?

For a search tool with full annotations, output schema, and clear parameters, the description covers everything needed: purpose, return fields, and follow-up actions. No gaps.

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 coverage is 100% with all parameters described. The description does not add additional parameter meaning beyond what's in the schema, but it does reinforce the parameter purpose (e.g., 'Company name (full or partial)'). Baseline 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 states the tool searches UK Companies House by company name and lists the returned fields. It also explicitly connects to sibling tools (get_officers, get_filings) by mentioning using company_number for lookups, distinguishing it from other search/lookup tools.

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 explains when to use the tool (to find a company by name) and provides examples in the schema. It implies alternatives when company_number is already known: 'Use the company_number to look up officers, filings, and PSCs.'

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

All Companies House toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources