Skip to main content
Glama

Bank Structural Events

bank_events
Read-onlyIdempotent

Per-bank structural-event timeline: M&A, charters, and closures. (Source: Federal Reserve NIC.)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 100, max 500).
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 readOnly=true, idempotent=true, openWorld=true, and destructive=false, so the safety profile is covered. The description contributes genuinely useful context by naming the upstream source (Federal Reserve NIC) and the event categories returned. It stops short of saying how the timeline is ordered, whether it is complete historical coverage, or how sparse results can be for small banks.

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?

Two compact sentences with the content types front-loaded and provenance parenthetically appended. Every clause carries information; nothing is redundant 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 simple read-only lookup with two parameters, one required, and full schema coverage, the definition supplies the essentials: what entity it keys on, what kinds of events appear, and where the data originates. Absent an output schema, a brief note on record shape or ordering would have made it complete, but no critical calling information is missing.

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 at the field level and the baseline of 3 applies. The description's 'per-bank' phrasing reinforces that rssd_id selects a single institution, but adds no pagination or ordering semantics for limit. Notably it does not address the mismatch between the limit field's stated max of 500 and the schema's maximum of 100.

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 and scope: a per-bank structural-event timeline covering M&A, charters, and closures, with data provenance (Federal Reserve NIC). That is enough to distinguish it from generic event feeds and from SEC-sourced alternatives, though it never explicitly contrasts itself with a sibling. It is a noun phrase rather than a verb-led statement, but the intent is unambiguous.

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 guidance, no preconditions, and no named alternative (e.g. SEC M&A events vs. this FR-sourced view). The only implied usage cue is 'per-bank', reinforced by the required rssd_id, so an agent must infer the selection context from the schema alone.

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