Skip to main content
Glama

Get Company Profile

company_profile
Read-onlyIdempotent

Fetch a company's full Companies House profile by number, including status, address, SIC codes, filing compliance flags, and outstanding charges. Use company search first to find the number.

Instructions

Fetch the full Companies House profile for a company number.

Returns status, registered address, SIC codes, filing compliance (overdue accounts and confirmation statement flags), and whether the company has outstanding charges. Use company_search first to find the company number.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_number": "<company_number>"
    },
    "name": "company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_numberYesCompanies House company number (8 digits, e.g. '03782379'). Returned by company_search.

Output Schema

NameRequiredDescriptionDefault
accountsNoAccounts filing status and due dates.
sic_codesNoStandard Industrial Classification codes.
has_chargesNoTrue if the company has at least one outstanding or part-satisfied charge (secured debt) — not yet fully discharged. False if every charge on record is fully satisfied, or there are none. Null if the charges check could not be completed, or if a charge was returned with an unrecognized status that can't be confidently classified. Use company_charges for the full charge-by-charge detail.
company_nameNoRegistered company name.
company_typeNoCompanies House company type code.
company_numberYesCompanies House company number.
company_statusNoCurrent status (active, dissolved, in liquidation, etc.).
date_of_creationNoIncorporation date (ISO YYYY-MM-DD).
confirmation_statementNoConfirmation statement filing status and next due date.
registered_office_addressNoRegistered office address as returned by Companies House.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.7.0
    • addedOutput schema / properties / accounts / properties / overdue / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / accounts / properties / overdue / default
      Previous value: -falseNew value: +null
    • changedOutput schema / properties / accounts / properties / overdue / description
      Previous value: -"True if accounts are past their due date at Companies House."New value: +"True if the accounts are past due at Companies House, false if Companies House says they are not. Null when Companies House returned no overdue flag (e.g. a registered overseas entity, or a missing block): unknown, NOT an all-clear."
    • removedOutput schema / properties / accounts / properties / overdue / type
      Removed value: -"boolean"
    • addedOutput schema / properties / confirmation_statement / properties / overdue / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / confirmation_statement / properties / overdue / default
      Previous value: -falseNew value: +null
    • changedOutput schema / properties / confirmation_statement / properties / overdue / description
      Previous value: -"True if the confirmation statement is past its due date."New value: +"True if the confirmation statement is past due at Companies House, false if Companies House says it is not. Null when Companies House returned no overdue flag (e.g. a registered overseas entity, or a missing block): unknown, NOT an all-clear."
    • removedOutput schema / properties / confirmation_statement / properties / overdue / type
      Removed value: -"boolean"
  2. Changed4 schema fields changedv1.3.0
    • addedOutput schema / properties / has_charges / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / has_charges / default
      Previous value: -falseNew value: +null
    • changedOutput schema / properties / has_charges / description
      Previous value: -"True if the company has outstanding registered charges (secured debt), derived from the /charges endpoint. A due diligence signal."New value: +"True if the company has at least one outstanding or part-satisfied charge (secured debt) — not yet fully discharged. False if every charge on record is fully satisfied, or there are none. Null if the charges check could not be completed, or if a charge was returned with an unrecognized status that can't be confidently classified. Use company_charges for the full charge-by-charge detail."
    • removedOutput schema / properties / has_charges / type
      Removed value: -"boolean"
  3. Addedv1.0.6
  4. Removedv1.0.1
  5. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuine behavioral context by listing what the response contains and which compliance signals it surfaces (overdue accounts, confirmation statement flags, outstanding charges), helping the agent decide whether this call answers its question.

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?

Front-loaded with verb plus resource in the first line, then the payload, then the prerequisite instruction. No filler, no restatement of the title, and each clause carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with a full output schema and complete annotations, the description covers purpose, expected contents, and the prerequisite call. It omits only edge behavior such as what happens for an unknown company number, which is minor here.

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% and the single parameter's format (8 digits, example '03782379', returned by company_search) is fully documented in the schema itself. The description's 'Use company_search first' repeats the schema's provenance hint rather than adding new meaning, so baseline 3 applies.

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?

States a specific verb and resource ('Fetch the full Companies House profile for a company number') and then enumerates the payload (status, registered address, SIC codes, compliance flags, charges), which separates it from narrower siblings like company_officers or company_charges.

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?

Gives an explicit entry condition: 'Use company_search first to find the company number', which tells the agent the required prerequisite and the sibling to run before this one. It does not state exclusions (e.g., when to prefer company_charges for charge detail), so it stops short of a full 5.

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