Skip to main content
Glama
Sign In
filing-agent

filing-agent

by chensirui3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_filings

Read-only

Lists a company's available SEC filings with document name, type, fiscal year, and page count so you can choose the filing matching your question's period before searching.

Instructions

List the filings available to search and read for a company: doc_name, type (10-K, 10-Q, 8-K, earnings release), fiscal year and page count. Use it to pick the filing that matches the question's period before searching.

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": {
      "company": "<company>"
    },
    "name": "list_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany name, ticker or CIK.
doc_typeNoOnly this filing type.
fiscal_yearNoOnly filings for this fiscal year.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and destructiveHint=false, so safety is covered; the description adds value by naming exactly what a caller receives (doc_name, type, fiscal year, page count), implying a compact metadata listing rather than document content. It does not mention ordering, pagination, or what happens when a company has no filings, which keeps it below a 5.

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?

Two sentences, zero waste: the first states what is listed and returned, the second states the selection workflow. Purpose is front-loaded before the usage instruction.

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?

With only three simple parameters, full schema coverage, and no output schema, the description supplies what an agent needs: the resource, the filterable dimensions, the returned fields, and the role in the workflow. Nothing material for correct invocation 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 100%, so the baseline is 3, but the description earns a bump by glossing the terse enum values ("10k", "10q", "8k") as human-readable labels (10-K, 10-Q, 8-K, earnings release). It still doesn't clarify filtering semantics such as whether doc_type and fiscal_year combine or how fiscal year is normalized.

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 opens with a specific verb and resource ("List the filings available to search and read for a company") and previews the returned fields (doc_name, type, fiscal year, page count). The trailing phrase "before searching" implicitly separates this listing step from the search/read siblings, so an agent can place it in the workflow without opening a schema.

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 explicit situational guidance: "Use it to pick the filing that matches the question's period before searching." That covers when to use and its ordering relative to search tools, but it names no when-not condition or alternative by name (e.g., search_filings).

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