Bradshaw UK funding rounds

Get filed accounts

get_company_financials

Read-onlyIdempotent

The balance-sheet history of one company from its filed accounts: cash, net assets, turnover, employees and the extraction flags, as filed. Source: UK Companies House filings (SH01 share allotments and the accounts filed with them). Every figure carries its working and a link to the filing page it was read from. Figures are as filed; nothing is guessed.

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": {
      "number": "<number>"
    },
    "name": "get_company_financials"
  }
}

Input Schema

Name	Required	Description	Default
`number`	Yes	UK company number: up to 8 letters and digits, for example 12203483 or SC123456.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the data source (UK Companies House SH01 filings), the guarantee that every figure carries its working and a link to the filing page, and the data-quality caveat that figures are as filed with nothing guessed. It does not discuss coverage gaps (e.g., companies with no filings) or response shape.

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 payload is front-loaded in the first clause and the remaining sentences add source and provenance rather than filler. There is mild redundancy: 'as filed' appears twice and 'nothing is guessed' restates the same assurance, which could be tightened.

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?

With one required parameter and no output schema, the description usefully compensates by naming the returned fields and the provenance of each figure. What remains thin is edge-case behavior for companies without filings and whether history is paginated or bounded in time.

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 100% schema description coverage, so the schema already explains the company number format and gives examples. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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: it returns the balance-sheet history of one company from filed accounts, and enumerates the fields (cash, net assets, turnover, employees, extraction flags). That is far more specific than the title 'Get filed accounts'. It does not explicitly contrast itself with get_company or get_company_rounds, so sibling differentiation is left to inference.

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?

Usage is implied rather than stated: 'one company' signals a single-company lookup keyed by company number, and the mention of UK Companies House hints at the applicable domain. There is no explicit when-to-use, when-not-to-use, or named alternative among the siblings such as get_company for general profile data.

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

All Bradshaw UK funding rounds 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?