Skip to main content
Glama

8-K Narrative Body

sec_8k_body
Read-onlyIdempotent

Item-by-item narrative bodies for one 8-K filing by accession number. (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": {
      "accession_number": "<accession_number>"
    },
    "name": "sec_8k_body"
  }
}

Input Schema

NameRequiredDescriptionDefault
accession_numberYesSEC accession number (e.g. 0001193125-24-000001).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the source (SEC EDGAR) and the single-filing scope, but says nothing about response size, per-item structure, or what happens for filings without narrative items.

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 short sentences with the resource and scoping constraint front-loaded and the source attribution kept as a parenthetical. No filler or redundant restatement of the title.

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 one-parameter read tool with full annotation coverage and no output schema, the description conveys enough to call it correctly: what is returned, for which filing, and from which source. A brief note on the per-item shape or behavior on filings lacking body text would make it fully 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 coverage is 100% and the single accession_number parameter already has a format example in the schema. The description confirms the parameter's role as the filing selector but adds no syntax, format, or edge-case detail beyond the schema, which is the expected baseline here.

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 ('item-by-item narrative bodies for one 8-K filing') and the lookup key ('by accession number'), so an agent knows exactly what it returns. It does not explicitly distinguish itself from the sibling sec_8k_events, which likely covers 8-K event metadata, leaving that discrimination to inference.

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?

Usage is only implied: the phrasing 'for one 8-K filing by accession number' signals you need a filing identifier and want the narrative text rather than a filing list. There is no explicit when-to-use, when-not-to-use, or named alternative such as sec_8k_events or sec_filings.

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