Skip to main content
Glama
kaylum54

companies-house-screening-mcp

by kaylum54

Find an officer

find_officer
Read-onlyIdempotent

Search Companies House by officer name to find directors, secretaries, or LLP members. Returns candidate officer IDs with appointment counts to identify the right person and get their appointments.

Instructions

Search Companies House for a company officer — a director, secretary or LLP member — by name. Returns candidate officer IDs with how many appointments each holds. Use it when you have a person and want the companies they are involved in; feed the officer_id to get_officer_appointments. Officer records are per-appointment-identity rather than per-person, so a common name returns many candidates and the appointment count and date of birth are usually what separates them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe officer's name.
verboseNoAlso return the untouched Companies House payload under `raw`, alongside the shaped result. Roughly two and a half times the size; use it only when a field you need is missing from the shaped result.
start_indexNoZero-based offset into the full result set. Use pagination.has_more to decide.
items_per_pageNoHow many records to return. Defaults to the API default; the maximum is 100.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoThe untouched Companies House payload. Present only when verbose was true.
metaYesProvenance and budget for this answer.
queryYes
officersYes
paginationYesWhere this page sits in the full result set.
Install Server

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already indicate read-only, open-world, idempotent, non-destructive behavior. The description adds valuable nuance beyond these: officer records are per-appointment-identity rather than per-person, common names return many candidates, and appointment count plus date of birth help disambiguate. This is precisely the behavioral context an agent needs.

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?

Three sentences with no filler: action and scope first, then the concrete use case and downstream step, then a crucial nuance about candidate identity. Every sentence earns its place and the structure flows logically.

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 description is complete for a search tool of this complexity. It explains what is returned, how to disambiguate candidates, and how to proceed afterward. The output schema and rich parameter descriptions cover the remaining details, so nothing essential is missing.

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%, and each parameter already has a clear description. The tool description adds useful result-interpretation context but no additional parameter-specific semantics. Baseline 3 is appropriate since the schema carries the parameter documentation 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 states a specific verb and resource: search Companies House for a company officer by name, listing officer types. It clearly differentiates from find_company and get_officers by focusing on person-name-based officer search and candidate officer IDs.

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?

It explicitly says when to use the tool: when you have a person and want the companies they are involved in. It also routes the caller to get_officer_appointments as the next step. It does not explicitly name alternatives or say when not to use it, but the context is clear.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kaylum54/companies-house-screening-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server