Skip to main content
Glama

FinanceQuery

SEC Filing Sections

get_filing_sections
Read-onlyIdempotent

Get sectioned text of one SEC filing by accession number (10-K or 8-K). Routes through EDGAR (best-effort HTML extraction) or Polygon when configured.

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": {
      "symbol": "<symbol>",
      "accession_number": "<accession_number>",
      "form": "<form>"
    },
    "name": "get_filing_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault
formYesWhich filing form to fetch sectioned text for: ten-k | eight-k
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesStock ticker symbol
accession_numberYesSEC accession number, e.g. "0000320193-24-000123"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world characteristics, and the description adds genuinely new behavioral context: the data may come from EDGAR with 'best-effort HTML extraction' or from Polygon 'when configured,' warning that output quality and source vary. It still does not say what happens if extraction fails or whether partial sections are returned.

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?

Two dense sentences with the core action front-loaded and the sourcing caveat second; no filler. It could be slightly tighter, but nothing is redundant or buried.

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

Completeness3/5

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

With no output schema, the description carries the burden of explaining what 'sectioned text' returns — section labels, structure, size, or truncation behavior are not described. For a simple four-parameter reader that gap is tolerable, but it leaves an agent guessing at the response shape.

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 description coverage is 100%, so all four parameters are already documented, including the ten-k/eight-k form values and accession number format. The description reinforces the accession-number and form axes but adds no syntax, defaults, or meaning beyond the schema — baseline 3 applies.

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?

States a specific verb and resource ('Get sectioned text of one SEC filing') and narrows scope to an accession number plus 10-K/8-K forms, which separates it from the broader EDGAR siblings like get_edgar_search and get_edgar_submissions. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than declared.

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 by the purpose statement — an agent can infer this is for reading the body text of a known filing. There is no explicit when-to-use, no prerequisite such as obtaining the accession number via get_edgar_submissions first, and no statement about when a sibling would be preferred.

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.