Skip to main content
Glama

Structural Events

events
Read-only

Industry-wide structural events: M&A, charters, closures. (Source: Federal Reserve NIC.)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 200, max 1000).
categoryNoEvent category filter, e.g. merger or charter_change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description's added value is the provenance note (Federal Reserve NIC), which tells the agent about coverage and authority of the data, but it says nothing about ordering, pagination behavior, or freshness.

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 fragments, content front-loaded, no filler words or repetition. It borders on under-specified rather than verbose, which is the right failure mode for this dimension but leaves no room for the routing and parameter context an agent needs.

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?

The tool is simple (zero required parameters, flat schema, no nested objects), so a short description is defensible. However, with no output schema present, the description should at least hint at what an event record contains (e.g., date, institution, event type), and it should say whether results are unpaginated or bounded.

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?

The description says nothing about limit or category filtering, but schema coverage is 100% and both parameters carry their own descriptions and examples, so the schema does the heavy lifting. The description neither contradicts nor extends them.

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 precisely and enumerates its contents (M&A, charters, closures) plus the underlying source (Federal Reserve NIC), so an agent knows what data comes back. The 'industry-wide' qualifier implicitly distinguishes it from per-institution siblings such as bank_events, but no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance. With siblings like bank_events, sec_8k_events, and sec_ma_events covering overlapping M&A/event territory, the agent is left to infer from 'industry-wide' alone whether this is the right scope.

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