sec-ai

by lkcair

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_filing_size

Read-onlyIdempotent

Check an SEC filing document's exact size before downloading to decide whether to read its text or share the link only.

Instructions

Get the exact size of a filing document BEFORE downloading it.

Use this to decide between reading the text (download_filing_text) and giving the user the link only. Sizes come from the EDGAR filing index.

Args: filing_url: Filing document URL (https://www.sec.gov/Archives/edgar/data/...)

Returns: size_bytes, size_mb, recommendation ('read_text' or 'link_only') and filing_url

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": {
      "filing_url": "<filing_url>"
    },
    "name": "get_filing_size"
  }
}

Input Schema

Name	Required	Description	Default
`filing_url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 21, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond them: the data source (EDGAR filing index) and the meaning of the returned 'recommendation' values. Slightly short of 5 only because it doesn't mention lookup failures for malformed URLs.

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?

Front-loaded with the core action, then the usage rule, then compact Args/Returns blocks. Every sentence earns its place with no redundancy.

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 one-parameter read-only lookup with an output schema, this covers purpose, usage routing, data provenance, and return contents. Nothing an agent needs to call it correctly is missing.

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 0% and the single property is documented only as 'Filing Url'. The description compensates by clarifying the parameter is a filing document URL and giving a concrete EDGAR URL pattern, adding real meaning beyond the schema.

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 ('Get the exact size of a filing document') plus a timing constraint ('BEFORE downloading it'), and explicitly distinguishes itself from the sibling download_filing_text. An agent can tell it apart from the other filing tools without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states the decision this tool supports — reading text via download_filing_text vs giving the user a link only — and names the alternative tool. The when-to-use condition is fully spelled out rather than left to inference.

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