Skip to main content
Glama

FiledProof

by com.filedproof
OverviewDiscussionsAdmin

List SEC filings

filedproof.list_filings
Read-onlyIdempotent

List recent or bounded historical SEC filings with canonical source metadata and explicit coverage limits. Use this when you need form, filing-date, or accession inventory, when choosing an exact pair for filedproof.compare_filings, or when confirming coverage before filedproof.check_disclosure_changes. For passage-level research, use filedproof.search_evidence instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formsNoSEC filing form types to include, such as 10-K, 10-Q, or 8-K.
limitNoMaximum number of operation-specific evidence or result records to return.
historyNoWhether to use bounded historical SEC submission archives when needed.
identifierYesTicker, CIK, or exact SEC company name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / forms / description
      Added value: +"SEC filing form types to include, such as 10-K, 10-Q, or 8-K."
    • addedInput schema / properties / history / description
      Added value: +"Whether to use bounded historical SEC submission archives when needed."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of operation-specific evidence or result records to return."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured FiledProof result with operation-specific evidence, provenance, coverage, and uncertainty fields.",
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing 'explicit coverage limits' and 'bounded historical SEC submission archives' via the history parameter, which tells the agent that results may be limited and historical depth is bounded. It doesn't describe pagination or exact return shape, but the output schema exists and the annotations cover the safety profile, so a 4 is appropriate.

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?

Three sentences with zero waste. The core purpose is front-loaded, followed by explicit use cases and a sibling alternative. Every sentence earns its place.

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?

Complete for a read-only list tool. The description covers what it returns (canonical source metadata), when to use it, and when not to use it. The output schema exists, annotations cover safety, and the parameter schema is fully documented. 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.

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all four parameters (forms, limit, history, identifier). The description adds context about 'canonical source metadata' and 'coverage limits' but doesn't add significant meaning beyond the schema. Baseline 3 is correct when the schema does the heavy lifting.

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?

The description states a specific verb ('List') and resource ('SEC filings') with clear scope: 'recent or bounded historical SEC filings with canonical source metadata and explicit coverage limits.' It also distinguishes itself from siblings by naming what it is not for ('For passage-level research, use filedproof.search_evidence instead'). This is a clear, specific purpose that an agent can act on.

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?

The description explicitly states when to use this tool: 'when you need form, filing-date, or accession inventory, when choosing an exact pair for filedproof.compare_filings, or when confirming coverage before filedproof.check_disclosure_changes.' It also names the alternative for passage-level research (filedproof.search_evidence). This is exemplary usage guidance with both positive and negative conditions.

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

All FiledProof 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