USERDATA

pull_filings

Stores current SEC filings by ticker and form type (e.g., 10-K, 8-K) to support traceable research and filing retrieval.

Instructions

Stores the latest filings of one form type, e.g. "10-K" or "8-K".

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": {
      "ticker": "<ticker>",
      "form_type": "<form_type>",
      "limit": "<limit>"
    },
    "name": "pull_filings"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	Yes
`ticker`	Yes
`form_type`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say whether filings are fetched live or cached, what 'latest' means (count, date window), whether the call persists state or has side effects, or whether any auth/rate limits apply. The word 'stores' is itself an undisclosed behavioral claim that leaves side-effect risk unresolved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, but its brevity reflects under-specification rather than economy given a three-parameter, three-required tool with no annotations. The form-type examples are the only well-spent words.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but the missing pieces are call-critical: the meaning of limit, the ticker format, and whether the operation is a read or a store. For a tool with 100% required params and zero schema descriptions, the description is too thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema coverage is 0%, so all three parameters (ticker, form_type, limit) depend on the description, yet only form_type is clarified via the '10-K'/'8-K' examples. ticker format (symbol vs CIK) and especially what limit bounds (number of filings? days back?) are undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (filings of one form type) and gives concrete form examples, but the verb 'stores' conflicts with the tool name 'pull_filings' and with siblings like pull_company/pull_prices, which clearly fetch data. An agent cannot tell whether this retrieves filings, persists them locally, or both, and no sibling is named or differentiated.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus pull_company, pull_facts, or pull_statements, nor any prerequisite or exclusion. The only implicit cue is 'latest filings', which the agent must infer.

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