Skip to main content
Glama
mikeyhu

companies-house-mcp

by mikeyhu

get_charge

Retrieve detailed information about a specific charge or mortgage registered against a UK company using the company number and charge ID.

Instructions

Get the detail of a single charge (mortgage) registered against a company.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
charge_idYes
company_numberYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
etagNo
linksNo
statusNo
created_onNo
acquired_onNo
charge_codeNo
particularsNo
resolved_onNo
delivered_onNo
satisfied_onNo
transactionsNo
charge_numberNo
classificationNo
secured_detailsNo
insolvency_casesNo
persons_entitledNo
scottish_alterationsNo
assets_ceased_releasedNo
covering_instrument_dateNo
more_than_four_persons_entitledNo
Behavior2/5

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

No annotations are provided, and the description only indicates a read operation ('Get'). It lacks details on authentication, rate limits, or any side effects beyond the obvious non-destructive nature.

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 a single concise sentence with no wasted words. However, it could be improved by adding brief parameter context.

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

Completeness2/5

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

Given the absence of annotations and the minimal description, the tool is under-documented. Even with an output schema, the description does not explain the return value or any edge cases, making it incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention or explain any parameters, and the input schema has no descriptions (0% coverage). The tool requires two parameters, but no context is provided for their format or usage.

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 clearly states the tool retrieves details of a single charge (mortgage) for a company, using a specific verb and resource, which distinguishes it from sibling tools like list_charges.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for fetching a specific charge, but it provides no explicit guidance on when to use it versus alternatives (e.g., list_charges) or any prerequisites.

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

Install Server

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/mikeyhu/companies-house-mcp'

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