Bradshaw UK funding rounds

Get funding signals

get_signals

Read-onlyIdempotent

Signals detected from filings, newest first: grant then equity, up round, lower-priced round, headcount surge, distress, foreign parent. 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": "get_signals"
  }
}

Input Schema

Name	Required	Description
`per`	No	Rows per page: 25 (default), 50 or 100.
`page`	No	Page number, from 1.
`rule`	No	grant_then_equity, up_round, lower_priced, headcount_surge, distress or foreign_parent (comma separated).
`sort`	No	detected (default newest first) or -detected / detected for the order.
`since`	No	Detected on or after: 30d, 12m or an ISO date.
`region`	No	Region slug(s) of the company.
`sector`	No	Bradshaw sector slug(s) of the company. A legacy SIC-group slug is still accepted here for backward compatibility; use sic_group.
`detected`	No	Detected window: same forms as filed, including from..to.
`sic_group`	No	SIC group slug(s) of the company: software-and-it, life-sciences-and-health, ...

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behaviour, so the safety profile is covered. The description goes further by disclosing ordering (newest first), provenance guarantees (every figure carries its working and a link to the filing page) and a no-inference policy (figures as filed, nothing guessed) — genuine behavioural context an agent could not get from the annotations. It stops short of stating result caps or pagination behaviour, which the schema handles.

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 signal taxonomy and the newest-first ordering are front-loaded, and the source is stated immediately after. The final two sentences partially overlap ('carries its working and a link to the filing page' versus 'as filed; nothing is guessed'), but each reinforces a different trust guarantee, so the redundancy is mild rather than wasteful.

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

Completeness3/5

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

There are nine optional parameters, no required input, and no output schema, so the description bears responsibility for describing the return shape. It does explain that results are figures with derivations and filing links, but it never describes the fields of a signal record itself (company, detection date, rule, magnitude), and it omits that the dataset is UK-only as a hard constraint. Adequate for orientation, not complete enough for confident invocation.

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 all nine parameters including rule, since, detected, region, sector and sic_group already carry their own semantics and examples. The description adds nothing parameter-specific — the signal names it lists merely mirror the rule values documented in the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

Names the resource (detected signals) and enumerates the concrete signal types returned (grant then equity, up round, lower-priced, headcount surge, distress, foreign parent), plus the source of truth. That is more than a restated title. However it never distinguishes itself from siblings like get_events, get_grants or search_rounds, which cover overlapping territory, so an agent still has to guess where the boundary lies.

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 only implied: the mention of UK Companies House SH01 allotments signals that this is a UK-filings-only feed, which implicitly excludes other jurisdictions and other data sources. There is no explicit when-to-use statement, no when-not-to-use, and no routing to the obvious alternatives such as get_events or get_company_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?