Bradshaw UK funding rounds

Get a company's funding rounds

get_company_rounds

Read-onlyIdempotent

The quality priced rounds of one company (confidence 0.5 or more, 100,000 pounds or more raised), newest filed first, each with price per share, valuation working and the filing link. Each round has post_money (as filed, counts deferred shares), valuation_verdict (quote, quote_with_care or never), post_money_ex_deferred and valuation_basis: quote a valuation only from post_money_ex_deferred, say so when the verdict is quote_with_care, and give none when it is never. 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_rounds"
  }
}

Input Schema

Name	Required	Description
`per`	No	Rows per page: 25 (default), 50 or 100.
`page`	No	Page number, from 1.
`sort`	No	filed (default), allotted, cash, price, stepup, post (post_money_ex_deferred) or conf; a leading - sorts descending.
`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

A4/5.0

Behavior5/5

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

Beyond the read-only and non-destructive annotations, it discloses confidence and funding thresholds, ordering, Companies House SH01 and accounts sources, as-filed figures, and the absence of guessing. It also explains valuation handling and per-figure working and filing-link provenance, which is substantial behavioral context.

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 scope and ordering are front-loaded, and the remaining sentences cover valuation semantics, sources, and provenance efficiently for a complex result. The second sentence is densely packed, and the working and filing-link details are somewhat repeated.

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?

With no output schema, the description usefully supplies the key returned fields, inclusion criteria, valuation interpretation rules, source, and evidence trail. Together with the fully documented input schema and safety annotations, it contains what an agent needs to invoke the tool and handle its results correctly.

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 description coverage is 100%, and number, per, page, and sort are already well documented there. The description reinforces the single-company scope and default filed ordering but adds little parameter-specific meaning beyond the schema.

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 clearly defines the resource as quality priced rounds for one company, with concrete inclusion thresholds, newest-filed-first ordering, and examples of returned content. It does not explicitly distinguish the tool from search_rounds or other siblings, so it falls short of the top score.

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 single-company scope implies when this tool is appropriate, and the valuation_verdict rules give useful guidance for presenting results. However, there is no explicit when-to-use or when-not-to-use guidance and no routing to search_rounds for cross-company discovery.

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?