Bradshaw UK funding rounds

Search funding rounds

search_rounds

Read-onlyIdempotent

Priced share-allotment rounds, newest filed first, with the shared filters (filed and allotted windows, sector, region, cash raised, post-money, step-up, confidence, press announced). Each round carries valuation_verdict and post_money_ex_deferred: quote a valuation only from post_money_ex_deferred, with care when the verdict is quote_with_care, and 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

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": "search_rounds"
  }
}

Input Schema

Name	Required	Description
`q`	No	Text inside the company name.
`per`	No	Rows per page: 25 (default), 50 or 100.
`cash`	No	Cash raised in pounds as lo..hi, either end optional, suffixes k, m, bn.
`conf`	No	Confidence range between 0 and 1.
`page`	No	Page number, from 1.
`post`	No	Post-money in pounds, same form as cash. Filters on post_money_ex_deferred (deferred shares left out), so a round with valuation_verdict never has no value and never matches.
`sort`	No	filed (default, newest first), allotted, cash, price, stepup, post (post_money_ex_deferred) or conf; a leading - sorts descending.
`filed`	No	Window the first filing was filed in: 7d, 30d, 90d, 12m, ytd or from..to (ISO dates, either end optional).
`region`	No	Region slug(s): london, south-east, scotland, ...
`sector`	No	Sector slug(s), comma separated or repeated: software-and-it, life-sciences-and-health, ...
`stepup`	No	up, flat, down (comma separated), or a price multiple range such as 1.5..
`company`	No	One company number.
`allotted`	No	Window the shares were allotted in; same forms as filed.
`announced`	No	yes: only rounds matched to a press announcement; no: only those not.
`press_link`	No	found: rounds with a matched press article; none: rounds we searched and found no press for (rounds not yet checked are in neither). Only while the press links feature is on.
`company_class`	No	public, vehicle, subsidiary or independent (comma separated). Default: all classes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), but the description adds genuinely unavailable-elsewhere behaviour: the data provenance (SH01 filings and accompanying accounts), the guarantee that every figure carries its working and a filing link, and the explicit rule that valuations may only be quoted from post_money_ex_deferred, with the quote_with_care and never verdict states called out. That is precisely the kind of trust/interpretation context annotations cannot convey.

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?

It front-loads what the tool returns and how it is ordered before the caveats, and no sentence is filler. The dense parenthetical filter list and the multi-clause valuation rule make parts of it a slow read, and the quoting protocol arguably belongs closer to the valuation concept it qualifies rather than tacked onto the search description.

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 16-filter tool with no output schema, the description covers the highest-risk unknown: which field a valuation may be quoted from and when it must be withheld, plus provenance and pagination via the schema's per/page. It does not sketch the wider shape of a returned round beyond valuation_verdict and post_money_ex_deferred, so the agent gets no overall picture of the record it will receive.

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%, so the schema already explains every one of the 16 filters, including the post filter's interaction with post_money_ex_deferred. The description's parenthetical list of filter families largely restates those parameters, adding only the framing that the filter set is 'shared' across search tools. Baseline 3 is the right level here.

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 opening clause names a specific resource and scope: 'Priced share-allotment rounds, newest filed first', plus the source (UK Companies House SH01 allotments). It is clear what the tool returns and roughly how it is ordered. It stops short of naming siblings such as get_company_rounds or search_companies, so the agent must infer that this is the market-wide search rather than the per-company lookup.

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 through the enumerated filters (filed/allotted windows, sector, region, cash, post-money, step-up, confidence, press) and the valuation-quoting rule, which tells the agent how to consume results. There is no explicit 'use this when… / use X instead' routing against get_company_rounds, get_events or search_companies, and no stated exclusions such as non-priced rounds.

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?