Bradshaw UK funding rounds

Get corporate investor

get_investor

Read-onlyIdempotent

One corporate shareholder family (from the register of people with significant control) and the companies it holds, each with a summary of its priced rounds. Use the key from the investors list. 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": {
      "key": "<key>"
    },
    "name": "get_investor"
  }
}

Input Schema

Name	Required	Description
`key`	Yes	The investor key, for example ACME FUND.
`per`	No	Rows per page: 25 (default), 50 or 100.
`page`	No	Page number, from 1.

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?

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the description does not need to repeat that. Instead it adds provenance the annotations cannot convey: the data comes from UK Companies House SH01 share allotments and the accounts filed alongside them, every figure carries its working and a link to the source filing, and figures are as filed rather than inferred. Pagination behavior is left to the schema, which keeps this a 4 rather than a 5.

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 description is front-loaded, opening with what the tool returns before moving to provenance, which is the right order for an agent scanning it. The closing pair of sentences is redundant, however: 'every figure carries its working and a link to the filing' and 'figures are as filed; nothing is guessed' largely restate the same trust guarantee.

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 no output schema, the description has to carry the burden of explaining what comes back, and it does: the investor, the companies it holds, and priced-round summaries with per-figure provenance. What is missing is minor for a read-only, closed-world tool: how paged results are returned, and what happens when a key is unknown.

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 three parameters are already documented, and that alone sets a baseline of 3. The description adds only a little beyond the schema: that `key` identifies a corporate shareholder family and is taken from the investors list. It says nothing further about `per` or `page` that the schema does not already cover.

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 names a specific resource: one corporate shareholder family from the PSC register, plus the companies it holds with a summary of each one's priced rounds. That is concrete enough that an agent can distinguish it from get_company (a single company) and search_rounds. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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 description gives one prerequisite: use the `key` from the investors list. It never says when to reach for this tool over get_company or search_rounds, or when it should not be used. The usage guidance is therefore implied rather than stated.

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?