Skip to main content
Glama

M&A Events (SEC)

sec_ma_events
Read-only

Mergers & acquisitions where this bank is on either side (SEC filings). (Source: SEC EDGAR 8-K / Schedule 13D.)

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": {
      "rssd_id": "<rssd_id>"
    },
    "name": "sec_ma_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 50, max 250).
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine value by naming the data provenance (SEC EDGAR 8-K / Schedule 13D), which hints that coverage is filing-driven and therefore partial; however, it never states that limitation outright, nor does it mention recency or result ordering.

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?

Two short clauses: the capability first, then the source in parentheses. Nothing is redundant and the scoping condition is front-loaded, though the tool name/title is partly restated.

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?

This is a simple two-parameter read tool with annotations and full schema coverage, so requirements are light. Still, the description doesn't say the tool returns filing-derived events only (so private deals are absent) or whether results are time-bounded, which an agent needs to interpret an empty response.

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 both rssd_id and limit are already documented. The phrase 'this bank' reinforces that rssd_id is the anchor, but nothing is added about limit behavior or what a null/empty result means, so the baseline 3 applies.

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 (mergers & acquisitions) and a specific scope constraint ('where this bank is on either side'), which is enough to distinguish it from generic bank/filing tools. It does not explicitly contrast with the sibling ma_screener, so it falls short of 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?

Usage is implied by the scope clause: use it to find M&A deals involving a given bank. There is no explicit when-to-use, no when-not-to-use, and no named alternative (e.g., ma_screener for the wider deal universe), leaving the agent to infer the boundary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources