Skip to main content
Glama

Companies House

by io.github.pipeworx-io

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

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
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

A3.6/5.0
Disambiguation2/5

Several tools have overlapping jobs: ask_pipeworx_beta is currently identical to ask_pipeworx, ask_pipeworx_grounded is the same router with stricter extraction, and discover_tools/suggest_questions both serve discovery. Company-facing tools also overlap (entity_profile vs recent_changes vs compare_entities), so an agent could easily route a query to the wrong tool despite detailed descriptions.

Naming Consistency3/5

Names are mostly snake_case and grouped prefixes like get_*, ask_pipeworx*, and polymarket_* are readable. However, conventions are mixed across the set: some are verb_noun (search_companies), some are noun phrases (entity_profile, deep_research, recent_changes), and the Companies House family sits awkwardly beside unrelated Pipeworx and prediction-market families.

Tool Count1/5

With 36 tools, the server is already heavy, but only five tools actually serve the named Companies House domain. The other 31 belong to Pipeworx querying, memory, subscriptions, and Polymarket trading, which is a severe mismatch between the server's stated purpose and its actual surface.

Completeness3/5

For UK company data, the core surface is mostly covered: search, company profile, filings, officers, and PSCs. However, charges and official document retrieval are missing even though get_company links to them, and the unrelated tools do nothing to complete the Companies House domain.

Resources