Skip to main content
Glama
Sign In

edgrapi-skills

by io.github.paperandbeyond23-gif
OverviewDiscussionsAdmin

Get an SEC filing document's text

get_filing_document
Read-onlyIdempotent

The text of one SEC filing document, fetched from the EDGAR archive by accession number (get it from get_filings). Omit file for the primary document (the 10-K, 8-K, Form 4...), or pass an exhibit filename. HTML is converted to plain text and returned in pages of max_chars; call again with offset = next_offset for the rest. Text documents only (HTML, XML, TXT).

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": "<accession>"
    },
    "name": "get_filing_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoCompany CIK. Needed when an agent or insider submitted the filing (Form 4, Form 144, many 8-Ks); get_filings returns it.
fileNoDocument filename within the filing; omit for the primary document.
offsetNoCharacter offset to start from (default 0).
accessionYesAccession number, e.g. '0000320193-26-000026'.
max_charsNoCharacters per page, 1,000-200,000 (default 40,000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real behavioral context beyond them: HTML is converted to plain text, output is paged by max_chars with a continuation offset, and only HTML/XML/TXT documents are supported.

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?

Three short sentences, front-loaded with what the tool returns, followed by selection and pagination mechanics. Dense but each clause carries operative information; only the parenthetical format examples are mild padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only fetcher with no output schema, the description covers the retrieval source, document selection, transformation (HTML to text), pagination loop and supported formats — everything needed to call it correctly and drive subsequent pages.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: it explains that omitting 'file' selects the primary document, that exhibits are selected by filename, and that 'offset' pairs with the previous response's next_offset for pagination. That is more than the schema's terse per-field text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('The text of one SEC filing document, fetched from the EDGAR archive') and explicitly distinguishes itself from the sibling get_filings by naming it as the source of the accession number. An agent can tell this is a single-document retrieval tool, not a search or listing tool.

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?

Gives concrete routing guidance: get the accession from get_filings, omit file for the primary document, pass an exhibit filename otherwise, and call again with offset = next_offset to page. It lacks an explicit 'when not to use this' exclusion beyond the text-only restriction, which keeps it just short of a 5.

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

All edgrapi-skills 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