Bradshaw UK funding rounds

Get corporate events

get_events

Read-onlyIdempotent

Corporate events from Companies House filings, Gazette notices and the PSC register: strike-off notices, liquidations, administrations, plc re-registrations, name changes, new corporate shareholders. Only event types that have passed their precision check are returned (see meta.live_types). Each event links to its filing or notice.

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_events"
  }
}

Input Schema

Name	Required	Description
`per`	No	Rows per page: 25 (default), 50 or 100.
`page`	No	Page number, from 1.
`type`	No	Event type(s), comma separated or repeated. Only types listed in `meta.live_types` are accepted.
`since`	No	Events dated on or after: an ISO date, or a span such as 30d or 12m.
`company`	No	One company number.

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 cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds valuable context about data provenance, the precision-check filtering constraint, and that each event links to its filing or notice, going beyond structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core resource and data sources, then adds only relevant constraints and linking behavior. Every sentence earns its place without repetition or unnecessary padding.

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 read-only listing tool with five optional, fully documented parameters, the description supplies enough context to call it correctly: sources, event types, precision filtering, and link behavior. It does not describe the full response shape or pagination metadata, but no output schema exists and the input schema handles pagination.

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 input schema already documents all five parameters. The description reinforces the type-filter constraint via meta.live_types but adds no new syntax or format detail beyond what the schema provides.

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 identifies the resource as corporate events from Companies House filings, Gazette notices, and the PSC register, and lists example event types. It is distinct from sibling tools like get_company or search_companies, though it lacks an explicit retrieval verb such as 'list' or 'fetch'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not state when to use this tool versus alternatives such as get_company or search_companies. Usage is only implied by the resource name and event examples, with no explicit when-to-use or when-not-to-use guidance.

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?