Skip to main content
Glama

get_sec_8k_events

Structured Form 8-K current reports from SEC EDGAR with item codes (2.02 Earnings, 5.02 Officer Changes), filing timestamps, and direct EDGAR URLs. $0.05.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum 8-K events to return (1-25, default: 10)
tickerNoOptional US stock ticker symbol (e.g. NVDA, AAPL). Defaults to watchlist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two genuinely useful behavioral traits beyond the schema: the upstream source (SEC EDGAR) and a per-call cost of $0.05, which lets an agent reason about spend. It says nothing about rate limits, latency, whether the whole watchlist is fanned out when no ticker is given, or what a missing-ticker or empty result looks like.

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?

A single dense sentence with no wasted words; the resource type and returned fields are front-loaded and the price is appended last. It is efficient, though it reads as a marketing line rather than structured guidance, which is why it isn't a 5.

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 simple two-parameter read tool with full schema coverage and no output schema, the definition covers source, contents, and cost. It leaves open the return shape details an agent would want (are items truncated, is there pagination, what does an empty result look like) and does not clarify the watchlist fan-out implied by the optional ticker.

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%: both `limit` (1-25, default 10) and `ticker` (optional, defaults to watchlist) are documented in the schema itself. The description adds no further parameter meaning, such as syntax constraints on ticker or whether item-code filtering is possible; 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 verb-and-resource pair: structured Form 8-K current reports from SEC EDGAR, with the concrete fields returned (item codes such as 2.02 Earnings and 5.02 Officer Changes, filing timestamps, EDGAR URLs). An agent can tell this is a raw filing-retrieval tool. It does not differentiate itself from siblings like analyze_sec_filing, which likely operates on the same filings at a deeper level, 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 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 or when-not-to-use guidance and no named alternative. The usage is only inferable from the resource name and the enumerated fields. An agent must guess whether this is the right entry point versus analyze_sec_filing or sec_analyst.

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