Skip to main content
Glama

Research data (x402)

filings_filings

$0.003 via x402: Filings for a company, newest first, filtered by form (10-K, 10-Q, 8-K, 4, 13F-HR, S-1 ...) and limited (up to 100): accession, form, filed and report dates, items, primary document URL. Pay 0.003 USDC through https://store.agentexchange.work/gw/filings/filings?ticker=NVDA&form=8-K&limit=20 Via the Agent Exchange store gateway; settled by Coinbase.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "filings_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNocik
formNoform
limitNolimit
tickerNoUS ticker (AAPL) or cik=<number>
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the price ($0.003 USDC via x402), the payment route and settlement provider, the ordering (newest first), and a hard limit cap of 100. It omits what happens on payment failure, rate limits, or pagination beyond the limit, which keeps it from 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.

Conciseness4/5

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

Dense and mostly front-loaded, with no filler sentences. The price tag is placed ahead of the purpose statement, which slightly buries what the tool does, and the inline store URL is long, but both carry real information.

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?

With no output schema and no annotations, the description does the necessary work by listing the return fields (accession, form, filed and report dates, items, primary document URL) and the payment protocol. Remaining gaps are edge-case behavior: what occurs when neither cik nor ticker is supplied despite an empty required list, and payment failure handling.

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 genuinely adds meaning the schema lacks: concrete form values (10-K, 10-Q, 8-K, 4, 13F-HR, S-1), the numeric ceiling on limit ('up to 100'), and a worked ticker example (NVDA). The relationship/alternative between cik and ticker is still left ambiguous.

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?

States a specific verb+resource ('Filings for a company, newest first') plus the filter dimensions (form) and cap (up to 100), and enumerates the returned fields. It does not differentiate itself from siblings like filings_search, filings_company, or filings_facts, which an agent would need in order to route correctly.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: an agent can infer 'per-company filing list filtered by form type', but there is no explicit when-to-use/when-not guidance against the other filings_* siblings. The payment flow ('without x_payment the answer is the price') lives only in the schema, not in the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources