Skip to main content
Glama

Companies House

by io.github.pipeworx-io

Get Officers

get_officers
Read-onlyIdempotent

List directors, secretaries, or LLP members for a UK company by company_number (from search_companies). Returns each officer's name, role, appointment/resignation dates, occupation, nationality, country of residence, and date of birth (month/year). Supports register_type filter (directors | secretaries | llp-members) and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_indexNoPagination offset (default 0)
register_typeNodirectors | secretaries | llp-members (optional restriction)
company_numberYesUK company number (e.g. "07098618") OR the company NAME (e.g. "Ocado Group") — a name is resolved here automatically and the match is echoed back as resolved_from_name. Pass whichever you have; do not guess a number from memory, since a plausible wrong one returns a clean officer list for a different company.
items_per_pageNo1-100 (default 35)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of officers
activeNoNumber of currently active officers
officersYesList of officers (directors, secretaries, etc.)
resignedNoNumber of resigned officers
company_numberYesUK company number

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safe-read profile is covered. The description adds useful context on the response fields (name, role, appointment dates, etc.) and the register_type filter, without contradicting annotations. It does not mention automatic name resolution, but that is present in the schema.

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: purpose, return content, and options. It is front-loaded with the verb 'List', contains no filler, and every sentence adds distinct information.

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 comprehensive schema (100% coverage), strong annotations, and an output schema, the description covers the essential usage flow (start from search_companies), the data returned, and available filters. It is sufficient for an agent to select and invoke the tool 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?

Schema description coverage is 100%, with each parameter fully described. The description restates the register_type filter and pagination but adds no new syntactic or semantic details beyond what the schema already provides. The company_number name-resolution behavior is only in the schema, not the description.

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 'List directors, secretaries, or LLP members for a UK company by company_number', a specific verb, resource, and scope. It clearly differentiates from sibling tools like get_persons_with_significant_control by naming officer roles explicitly.

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 says 'from search_companies', which implies a prerequisite lookup step and provides clear context for when to use this tool. However, it does not explicitly mention alternatives like get_persons_with_significant_control or state when not to use this tool, so it falls short of full alternative guidance.

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