Skip to main content
Glama
Sign In

SEC EDGAR

by io.github.guptaprakhariitr
OverviewDiscussionsAdmin

edgar_read_filing

Fetch the full text (HTML) of a specific filing by accession number. Useful when the user wants to read the actual content of a 10-K/8-K. Truncates at ~80K characters; use search to narrow first.

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

Input Schema

NameRequiredDescriptionDefault
cikNo10-digit CIK (zero-padded). Used to construct the document URL.
tickerNoStock ticker (used to resolve the CIK; pass either this or cik).
accession_numberYesAccession number, e.g. '0001564590-24-029333'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Discloses truncation behavior, which is important. However, with no annotations provided, it does not cover other aspects like error handling, response format, or authentication requirements.

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 sentences, no wasted words. Front-loaded with the primary action and resource. Efficient and clear.

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?

Fairly complete for a 3-parameter tool with no output schema. Covers purpose, use case, and truncation limitation. Could mention error conditions or optional params, but is sufficient.

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 baseline 3 applies. Description adds minimal extra meaning beyond the schema, just reinforcing accession number usage. No new parameter insights.

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 states it fetches full text HTML of a specific filing by accession number, and mentions usefulness for 10-K/8-K. It is clear but does not explicitly differentiate from sibling tools like edgar_get_8k.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides a when-to-use context (reading actual content of 10-K/8-K) and a limitation (truncation at ~80K characters, recommends using search first). Does not specify when not to use or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SEC EDGAR toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources