Skip to main content
Glama
paulieb89

UK Due Diligence

by paulieb89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Company Officers

company_officers
Read-onlyIdempotent

Fetch UK company officers by company number, returning directors, secretaries, appointment dates, nationality, and residence. Resigned officers are excluded unless include_resigned is set.

Instructions

Fetch officers for a Companies House company number.

Returns directors, secretaries, and other officers with appointment dates, nationality, and country of residence. Resigned officers are excluded by default; set include_resigned=true for historical DD. Pagination is handled internally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_indexNoIgnored — pagination is handled internally. Only accepted to avoid call failures.
company_numberYesCompanies House company number (8 digits, e.g. '03782379'). Returned by company_search.
items_per_pageNoIgnored — pagination is handled internally. Only accepted to avoid call failures.
include_resignedNoInclude resigned/historic officers. Default false for backwards-compatible current-officer queries.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal officers returned (filtered by include_resigned).
officersNoOfficer records.
company_numberYesCompanies House company number.
include_resignedYesWhether resigned officers were included in this result.
high_appointment_count_flagNoNumber of active officers with 10+ total appointments, or null if appointment counts were not fetched. Non-zero values are a nominee/phoenix director risk signal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / properties / include_resigned
      Added value: +{
+  "default": false,
+  "description": "Include resigned/historic officers. Default false for backwards-compatible current-officer queries.",
+  "type": "boolean"
+}
    • changedInput schema / properties / start_index / description
      Previous value: -"Ignored — all officers are returned in one call."New value: +"Ignored — pagination is handled internally. Only accepted to avoid call failures."
    • addedOutput schema / properties / officers / items / properties / officer_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Companies House officer ID, extracted from links.officer.appointments. Pass to officer_appointments to discover this person's full appointment history across companies, including dissolved or insolvent ones."
+}
  2. Addedv1.0.6
  3. Removedv1.0.1
  4. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds genuine behavioral context beyond the annotations: the default exclusion of resigned officers, the flag to include them for historical due diligence, and the fact that pagination is handled internally. These are meaningful traits not inferable from the schema or annotations alone.

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 concise sentences with no filler: it leads with the core purpose, lists returned data, and then covers the important defaults and pagination behavior. Every sentence earns its place.

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 read-only list tool with an output schema, full parameter documentation, and safety annotations, the description covers all necessary operational details: scope, returned fields, default behavior, the optional flag, and pagination. Nothing that an agent needs to call it correctly is missing.

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 the baseline is 3. The description adds value by explaining that pagination is handled internally, which clarifies why start_index and items_per_page are ignored, and by stating the default behavior of include_resigned. This goes beyond the parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Fetch officers for a Companies House company number') and enumerates the officer types and returned fields. It clearly distinguishes the tool's function, though it does not explicitly contrast it with sibling tools like officer_appointments or company_profile.

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 gives clear invocation context: what data is returned, that resigned officers are excluded by default, and when to set include_resigned=true for historical data. It does not explicitly name alternative tools or when not to use this one, but the scope is specific enough for an agent to select it appropriately.

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

Deploy Server

Other Tools