Skip to main content
Glama

get_8k_material_events

Read-only

Use when monitoring material issuer events via recent 8-K filings for a ticker. Returns 8-K filing metadata from EDGAR submissions with optional item-code filter hints. Source: SEC EDGAR submissions. $0.10 USDC per call.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_8k_material_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
days_backNo
item_codesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the upstream source (SEC EDGAR submissions), the shape of the return (filing metadata), and a metered cost of $0.10 USDC per call, which matters for agent budgeting. It stops short of describing pagination, coverage windows, or empty-result behavior.

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?

Four short sentences, front-loaded with the trigger condition and followed by return shape, source and price — every sentence carries information. Minor deduction for the vague phrase "filter hints", which costs precision without saving much length.

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, three-parameter tool with no output schema, the definition covers source, return type, cost and the optional filter well enough to invoke it. The remaining gaps are the semantics of the date window and the exact matching rules for item codes, which an agent would need for confident filtering.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must carry the load, and it only gestures at two of them: ticker implicitly and item_codes as "optional item-code filter hints" — "hints" is ambiguous about whether codes are matched exactly or broaden the query. days_back is never mentioned, nor are its 1–90 bounds, and no item-code format example is given.

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 (8-K filing metadata from SEC EDGAR submissions) and a specific scoping key (a ticker), so an agent knows exactly what it retrieves. It does not distinguish itself from any named alternative, which is the only thing separating it from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when monitoring material issuer events via recent 8-K filings" frames a trigger condition, but it largely restates the tool's own purpose rather than contrasting it with an alternative or stating when not to use it. There is no guidance on how this differs from other filing- or event-oriented tools, leaving selection reasoning implicit.

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