Skip to main content
Glama

8-K Material Events

sec_8k_events
Read-only

8-K filings broken out by item number, the SEC material-event feed. (Source: SEC EDGAR 8-K.)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax item rows to return (default 100, max 500).
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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data status are covered. The description adds provenance (SEC EDGAR 8-K) and the item-level row granularity, but says nothing about latency, coverage window, or what happens when a filing has no items.

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 sentences, front-loaded with the resource and its granularity. Slight redundancy in repeating '8-K' three times and a parenthetical source note that could be folded in, but nothing is bloated.

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?

A two-parameter read tool with no output schema, so return-shape explanation is not required. However, the description never clarifies the item-row concept the agent will actually receive, and it does not resolve the limit discrepancy (schema says maximum 100, its own param text says max 500), leaving the agent's expectations ambiguous.

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 coverage is 100%, so both rssd_id and limit are documented in the schema itself. The description contributes no additional parameter meaning (e.g., which identifier namespace rssd_id belongs to), so 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?

States a specific resource (8-K filings) and its granularity ('broken out by item number'), plus the upstream source (SEC EDGAR 8-K). This implicitly separates it from a whole-filing sibling like sec_8k_body, but the distinction is never stated explicitly, so the agent must infer it.

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 exclusions, and no pointer to alternatives such as sec_8k_body or bank_events. The agent must decide on its own whether it wants item-level rows or full filing text.

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