UK Data for Agents

company_charges

Read-onlyIdempotent

Registered charges and mortgages (secured debt) against a UK company number: status, amounts, who the debt is owed to. For credit, lending and due-diligence checks. (cost: 1 credit)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "company_charges"
  }
}

Input Schema

Name	Required	Description	Default
`companyNumber`	No	string, required

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new information the annotations lack: the operation costs 1 credit and the input must be a UK company number. It does not say what happens when a company has no charges, which is the main remaining gap.

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?

Two short sentences, front-loaded with what is returned and followed by the intended audience and cost. Nothing is redundant or padded.

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 one-parameter read-only lookup with no output schema, the description covers what data comes back, who it is for, and the credit cost. Only the empty-result behavior and whether historical charge filings are included are left unstated.

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?

There is a single parameter with full schema coverage, so the baseline is 3. The description adds only the qualifier that the number must be a UK company number; it provides no format or example beyond that.

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 names a specific resource ('registered charges and mortgages (secured debt) against a UK company number') and enumerates the returned facets (status, amounts, creditor). This is clearly distinguishable from siblings like company_insolvency or company_filings without opening any schema.

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?

It gives use-case context ('For credit, lending and due-diligence checks') which implies when to reach for it, but never states when-not to use it or names an alternative sibling such as company_insolvency for distress signals. Guidance is implied rather than explicit.

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

All UK Data for Agents tools Inspect

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

Need Help?