Skip to main content
Glama
Sign In

Edgrapi — US Government Data API

by com.edgrapi.api
OverviewDiscussionsAdmin

Get 10-K/10-Q/S-1 narrative sections

get_sections
Read-onlyIdempotent

Narrative sections from the latest 10-K/10-Q as clean text — Risk Factors (item 1A), MD&A (item 7), Business (item 1), etc. — or from an IPO registration statement (form 'S-1'): risk_factors, use_of_proceeds, mda, business, principal_stockholders, shares_eligible. Built for LLM/RAG equity research. Omit 'item' to list the available sections first. For a company that hasn't listed yet, pass its CIK as 'ticker'.

Input Schema

NameRequiredDescriptionDefault
formNoFiling type: '10-K' (default), '10-Q', 'S-1' (latest S-1 or S-1/A) or 'S-1/A'.
itemNoSection to fetch, e.g. '1A' (Risk Factors) or '7' (MD&A) for a 10-K, or 'risk_factors' / 'use_of_proceeds' for an S-1. Omit to list available sections.
tickerYesUS stock ticker, e.g. 'AAPL'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / form / description
      Previous value: -"Filing type: '10-K' (default) or '10-Q'."New value: +"Filing type: '10-K' (default), '10-Q', 'S-1' (latest S-1 or S-1/A) or 'S-1/A'."
    • changedInput schema / properties / item / description
      Previous value: -"Section to fetch, e.g. '1A' (Risk Factors) or '7' (MD&A). Omit to list available sections."New value: +"Section to fetch, e.g. '1A' (Risk Factors) or '7' (MD&A) for a 10-K, or 'risk_factors' / 'use_of_proceeds' for an S-1. Omit to list available sections."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description adds that output is clean text tuned for LLM/RAG, that omitting 'item' returns a section listing, and that CIK works as a ticker substitute. It does not disclose output size/truncation limits, which matters for a tool returning whole 10-K sections into a context window.

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 tight sentences, front-loaded with what is returned before the section enumeration and the operational hints. Dense with parenthetical item codes but no filler; slight nesting ('form \'S-1\'') makes it busier than strictly necessary.

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?

No output schema exists, so the description carries the return-shape burden and does so adequately: text sections, section-listing mode, and pre-IPO ticker handling. Missing is behavior on invalid/missing sections and whether long sections are chunked or truncated — the main remaining unknown for an agent calling it.

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 3 is the floor, but the description adds real meaning: it enumerates valid S-1 item keys and clarifies that 'ticker' accepts a CIK for unlisted issuers — a case the schema's 'US stock ticker, e.g. AAPL' actively contradicts. It also restates the omit-item listing behavior beyond the schema 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 — narrative sections (Risk Factors, MD&A, Business) as clean text from 10-K/10-Q, and named S-1 sections (risk_factors, use_of_proceeds, mda, etc.). The enumerated section keys make it immediately distinguishable from get_filings and get_xbrl, which provide filings lists and financial data rather than narrative text.

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 advice: omit 'item' to list available sections first, and pass a CIK as 'ticker' for pre-IPO companies. Clear context for when each mode applies, though it never explicitly names a sibling tool as the alternative for filing-list or XBRL lookups.

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

All Edgrapi — US Government Data API 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