Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Newest SEC EDGAR filings across ALL companies in one call (form=8-K default, also 10-K, 10-Q, 4, S-1, 13F-HR; count 10,

filings_latest
Read-onlyIdempotent

Newest SEC EDGAR filings across ALL companies in one call (form=8-K default, also 10-K, 10-Q, 4, S-1, 13F-HR; count 10, 20, 40, 80 or 100): company, CIK, accession, filed time, 8-K items, document index link. One poll replaces per-ticker polling. Pay per call $0.002 USDC on Base via x402.

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_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNo8-K (default), 10-K, 10-Q, 4, S-1
countNo10, 20, 40, 80 or 100
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the description earns credit for going beyond them: it discloses the pay-per-call cost ($0.002 USDC on Base via x402) and the first-call-then-pay handshake. It also enumerates the response fields (company, CIK, accession, filed time, 8-K items, document index link), which is useful since no output schema exists.

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 core purpose is front-loaded, but the sentence is a single sprawling run-on with parenthetical enumerations of forms, counts and return fields. It is dense but not wasteful; readability suffers from cramming everything into one sentence.

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?

For a three-parameter, zero-required read tool with no output schema, the description covers scope, defaults, return fields and the payment flow an agent must handle. The only notable gap is that the payment retry behavior is only implied by the schema's x_payment description rather than spelled out here.

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 three parameters. The description duplicates the form and count value lists and only marginally extends the schema by mentioning 13F-HR, which the schema's form description omits. Baseline 3 applies.

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?

Starts with a specific verb and resource: 'Newest SEC EDGAR filings across ALL companies in one call', and scopes it with 'One poll replaces per-ticker polling'. An agent immediately knows this is a market-wide filing feed rather than a single-issuer lookup, though it never names a sibling tool for comparison.

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?

The phrase 'One poll replaces per-ticker polling' implies when to prefer this over per-company queries, but there is no explicit when-to-use or when-not-to-use statement and no named alternative. Usage is inferable rather than directed.

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