Skip to main content
Glama

capabilities

by com.eckari
OverviewDiscussionsAdmin

Check UK company accounts due dates on Companies House

company_uk_accounts
Read-onlyIdempotent

Return the accounts filing status of a UK company from the Companies House register — the accounting reference date, the last accounts filed (type and period), the next accounts due date and a derived overdue flag. Use when: When are this UK company's accounts due? Not for: You need financial figures (turnover, profit, balance sheet) — not on the public register API. Related: company_uk_filings; company_uk_profile; company_uk_status. Price: USD 0.003/call (x402), 0.002 (account key).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_numberYesCompanies House company number, also called the company registration number (CRN). Accepted shapes are the register's own — 1-8 digits (zero-padded to 8, e.g. 445790 → 00445790), one letter + 7 digits (R0000001), two letters + 6 digits (SC002180, NI000001, OC123456, OE000001), or the registered-society suffix forms (two letters + 5 digits + 1 letter; two letters + 4 digits + 2 letters). Case-insensitive; surrounding whitespace is ignored (which is why maxLength is 10); internal spaces and punctuation are not accepted. Any other value (for example PROBE) is rejected as INVALID_INPUT before payment and before any upstream call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesCapability output; full JSON Schema at https://api.eckari.com/v1/capabilities/company.uk.accounts
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / company_number / description
      Previous value: -"Companies House company number, also called the company registration number (CRN). The identifier itself is 1-8 letters/digits; surrounding whitespace is ignored (which is why maxLength is 10), but the value must not contain internal spaces. Short numeric values are zero-padded to 8 characters. A whitespace-only or over-long value is rejected as INVALID_INPUT before any payment or upstream call."New value: +"Companies House company number, also called the company registration number (CRN). Accepted shapes are the register's own — 1-8 digits (zero-padded to 8, e.g. 445790 → 00445790), one letter + 7 digits (R0000001), two letters + 6 digits (SC002180, NI000001, OC123456, OE000001), or the registered-society suffix forms (two letters + 5 digits + 1 letter; two letters + 4 digits + 2 letters). Case-insensitive; surrounding whitespace is ignored (which is why maxLength is 10); internal spaces and punctuation are not accepted. Any other value (for example PROBE) is rejected as INVALID_INPUT before payment and before any upstream call."
    • changedInput schema / properties / company_number / pattern
      Previous value: -"^\\s*[A-Za-z0-9]{1,8}\\s*$"New value: +"^\\s*(?:[0-9]{1,8}|[A-Za-z][0-9]{7}|[A-Za-z]{2}[0-9]{6}|[A-Za-z]{2}[0-9]{5}[A-Za-z]|[A-Za-z]{2}[0-9]{4}[A-Za-z]{2})\\s*$"
  2. Changed3 schema fields changed
    • removedInput schema / properties / companyNumber
      Removed value: -{
-  "description": "Companies House company number, also called the company registration number (CRN). The identifier itself is 1-8 letters/digits; surrounding whitespace is ignored (which is why maxLength is 10), but the value must not contain internal spaces. Short numeric values are zero-padded to 8 characters. A whitespace-only or over-long value is rejected as INVALID_INPUT before any payment or upstream call.",
-  "maxLength": 10,
-  "minLength": 1,
-  "pattern": "^\\s*[A-Za-z0-9]{1,8}\\s*$",
-  "type": "string"
-}
    • addedInput schema / properties / company_number
      Added value: +{
+  "description": "Companies House company number, also called the company registration number (CRN). The identifier itself is 1-8 letters/digits; surrounding whitespace is ignored (which is why maxLength is 10), but the value must not contain internal spaces. Short numeric values are zero-padded to 8 characters. A whitespace-only or over-long value is rejected as INVALID_INPUT before any payment or upstream call.",
+  "maxLength": 10,
+  "minLength": 1,
+  "pattern": "^\\s*[A-Za-z0-9]{1,8}\\s*$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "companyNumber"
-]New value: +[
+  "company_number"
+]
  3. Changed7 schema fields changed
    • removedOutput schema / properties / data / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / data / description
      Previous value: -"Contains public sector information licensed under the Open Government Licence v3.0 (Companies House)."New value: +"Capability output; full JSON Schema at https://api.eckari.com/v1/capabilities/company.uk.accounts"
    • removedOutput schema / properties / data / properties
      Removed value: -{
-  "accounting_reference_date": {
-    "additionalProperties": false,
-    "description": "The register's accounting reference date (ARD) as a day and month with no year: the anchor Companies House uses to derive a company's accounting periods and filing deadlines. It is not the same thing as the end date of any particular set of accounts — a company filing to a 52/53-week calendar may make its accounts up to any date within seven days either side of the ARD, so read last_accounts.made_up_to for the actual period end. TESCO PLC's ARD is 26 February while its last accounts were made up to 28 February 2026.",
-    "properties": {
-      "day": {
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "month": {
-        "type": [
-          "integer",
-          "null"
-        ]
-      }
-    },
-    "type": [
-      "object",
-      "null"
-    ]
-  },
-  "company_name": {
-    "type": "string"
-  },
-  "company_number": {
-    "type": "string"
-  },
-  "has_accounts_information": {
-    "description": "Derived; false when the register holds no accounts block for this company.",
-    "type": "boolean"
-  },
-  "last_accounts": {
-    "additionalProperties": false,
-    "properties": {
-      "made_up_to": {
-        "format": "date",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "period_end_on": {
-        "format": "date",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "period_start_on": {
-        "format": "date",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "type": {
-        "description": "Register accounts type (e.g. full",
-        "dormant": null,
-        "group).": null,
-        "micro-entity": null,
-        "small": null,
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": [
-      "object",
-      "null"
-    ]
-  },
-  "next_accounts": {
-    "additionalProperties": false,
-    "properties": {
-      "due_on": {
-        "format": "date",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "overdue": {
-        "type": [
-          "boolean",
-          "null"
-        ]
-      },
-      "period_end_on": {
-        "format": "date",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "period_start_on": {
-        "format": "date",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": [
-      "object",
-      "null"
-    ]
-  }
-}
    • removedOutput schema / properties / data / required
      Removed value: -[
-  "company_number",
-  "company_name",
-  "has_accounts_information",
-  "accounting_reference_date",
-  "last_accounts",
-  "next_accounts"
-]
    • addedOutput schema / properties / meta / properties / attribution_url
      Added value: +{
+  "format": "uri",
+  "type": "string"
+}
    • addedOutput schema / properties / meta / properties / retrieved_at / format
      Added value: +"date-time"
    • addedOutput schema / properties / meta / required
      Added value: +[
+  "capability",
+  "version",
+  "retrieved_at",
+  "source",
+  "freshness",
+  "request_id"
+]
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond those annotations: the derived overdue flag, the fact that financial figures are not available through the register API, and per-call pricing. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well front-loaded with the primary purpose and output, then efficiently covers usage, exclusions, related tools, and pricing. Each section earns its place, though the pricing detail is slightly tangential to tool selection and invocation.

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 one required parameter with thorough schema documentation, an output schema, and clear usage boundaries, the description is complete. It tells the agent what the tool returns, when to use it, when not to use it, and how it relates to siblings. Nothing essential is missing for correct selection and invocation.

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?

The schema fully covers the single parameter with a detailed explanation of accepted company number formats and rejection behavior. Since schema coverage is 100%, the description does not need to compensate, and it provides no additional parameter-level meaning beyond the schema.

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 uses a specific verb and resource: 'Return the accounts filing status of a UK company from the Companies House register.' It also enumerates the exact outputs (accounting reference date, last accounts filed, next due date, overdue flag), which clearly distinguishes it from siblings like company_uk_profile or company_uk_filings.

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 an explicit trigger ('When are this UK company's accounts due?') and a clear exclusion ('Not for: You need financial figures'). It names related sibling tools, though it does not fully explain when each of those siblings should be chosen instead. This is clear context but stops short of a complete routing guide.

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

All capabilities toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources