Skip to main content
Glama

BankRegReports

Financial Restatements (8-K Item 4.02)

restatements
Read-only

Non-reliance / financial-restatement events (8-K Item 4.02) filed by this bank's registrant. (Source: SEC EDGAR 8-K (Item 4.02).)

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

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

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?

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description is consistent with those by identifying SEC EDGAR as the source. It adds the registrant scope but does not disclose return shape, pagination, empty-result behavior, or authentication/rate-limit context. No annotation contradiction is present.

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 definition is a single concise sentence plus a source note, with the event type and item number front-loaded. The repeated '8-K Item 4.02' in the source parenthetical is slightly redundant but not materially wasteful.

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?

For a one-parameter, read-only lookup with no output schema, the description supplies the essential scope and data source. It remains thin on what the response contains and why a caller should choose it over broader event tools, so it is adequate but not complete.

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%, and the single rssd_id parameter is documented in the schema as a Federal Reserve RSSD id with an example. The description's phrase 'this bank' reinforces the entity meaning but adds no format or selection guidance beyond the schema, so this meets the baseline.

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 the exact resource (8-K Item 4.02 non-reliance/financial-restatement events) and the entity scope (this bank's registrant). It is specific, but it uses a noun phrase without an explicit verb like 'list' or 'return', and it does not explicitly distinguish itself from generic event sibling tools.

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 explicit when-to-use guidance, no mention of alternatives such as events or bank_events, and no stated prerequisites. The specific event type implies the use case, but an agent must infer that this tool should be selected only for restatement queries.

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