Skip to main content
Glama
Sign In
filing-agent

filing-agent

by chensirui3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

read_filing_page

Read-only

Read a full SEC filing page with table columns aligned and detected statement type and units, so you verify scale and periods before taking a number. Optionally include adjacent pages when tables continue.

Instructions

Read one page of a filing in full, with table columns aligned, plus the page's statement type and units line (e.g. 'In millions, except per share data') when detected. Read the full page before taking a number from a table: check the units and which column is which period. include_neighbors adds the pages before and after.

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": {
      "doc_name": "<doc_name>",
      "page": "<page>"
    },
    "name": "read_filing_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesZero-based page number, as search results give it.
doc_nameYesFiling id, e.g. 3M_2018_10K.
include_neighborsNoAlso return the previous and next pages (tables often continue).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description usefully adds what the returned text looks like (aligned columns, detected statement type, units line) and what include_neighbors pulls in, but says nothing about out-of-range pages, page-count limits, or failure modes beyond the annotations' coverage.

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 the what, then the usage rule, then the optional flag. The units example is illustrative rather than filler; only the include_neighbors sentence partly duplicates the schema.

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 read-only, three-parameter tool with no output schema, the description conveys the shape of the returned content and the key caveat about units and periods, which is what an agent needs to use the result correctly. It is not quite complete on boundary behavior (invalid page numbers, start/end of document).

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 every parameter already carries a description, so the baseline is 3. The description restates include_neighbors' neighbor behavior without adding new meaning and adds no format or range detail for page or doc_name beyond what the schema states.

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 opens with a specific verb and resource ('Read one page of a filing in full') and enumerates what the page contains: aligned table columns, statement type, and units line. It never names a sibling or states what it is not, so an agent must infer the contrast with search_filings from context rather than from explicit differentiation.

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?

It gives concrete workflow guidance – read the full page before taking a number from a table, and check units and period columns – plus a clear conditional for include_neighbors when tables continue. It stops short of naming when to use this instead of search_filings or the xbrl_* tools, so alternatives remain implicit.

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

Deploy Server

Other Tools