Lordevo Shop (x402 website checks)

SEC EDGAR filings of a listed company ($0.002/call)

sec_filings

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Public records] Recent SEC EDGAR filings of a US-listed company by ticker (AAPL, BRK-B) or CIK: company name, CIK, tickers, exchanges, SIC industry, fiscal year end and state of incorporation, then the filings (form, filing and report date, accession number, description, 8-K items, XBRL flag, document and index URLs), filtered by form types and date, with counts per form. Listed companies only (CIKs in the SEC ticker list; no individuals). Documents are linked, not read. No key; cached 10 min. ~0.5-3 s.

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": "sec_filings"
  }
}

Input Schema

Name	Required	Description	Default
`forms`	No	Comma list of form types to keep, e.g. 10-K,10-Q,8-K (amendments like 10-K/A are included); default all
`since`	No	Filed on or after this date, YYYY-MM-DD
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.
`company`	Yes	Stock ticker of a US-listed company (AAPL, BRK-B) or its SEC CIK number (320193)
`max_results`	No	Filings returned, 1-100 (default 20); matched is always the full count in the recent list	20

Output Schema

Name	Required	Description
`tool`	No
`cache`	No
`notes`	No
`_trial`	No	Present when the call was a free trial call.
`filter`	No
`source`	No
`company`	No
`filings`	No
`matched`	No
`provider`	No
`returned`	No
`price_usd`	No
`truncated`	No
`fetched_at`	No
`attribution`	No
`form_counts`	No
`response_ms`	No
`recent_total`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / trial / description

Previous value: -"Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms."New value: +"Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms."

AddedNov 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, it discloses pricing ($0.002/call, USDC on Base via x402), the free-trial mechanism (trial: true, 3 per IP per UTC day), that no key is required, a 10-minute cache, and an expected latency of ~0.5-3 s. That is exactly the operational context the annotations cannot convey.

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?

Pricing and trial information are placed up front, followed by scope and output content, and everything is compressed into one dense paragraph. The result is efficient, though the enumeration of returned fields is somewhat long, and because an output schema exists, part of that enumeration is redundant.

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?

The definition covers pricing, payment method, free-trial limits, authentication (none), caching, latency, scope restrictions, and what is returned and what is linked rather than read. Because an output schema exists, the full return-value behavior does not need to be explained; this description is complete for correct invocation.

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 each parameter, including forms, since, trial, company, and max_results. The description adds only a summary-level statement that results are 'filtered by form types and date, with counts per form'. The explanation of individual parameter semantics is left to the schema, so the baseline of 3 is appropriate.

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 names a specific verb and resource: 'Recent SEC EDGAR filings of a US-listed company by ticker (AAPL, BRK-B) or CIK'. It distinguishes itself from the sibling federal_register tool because it describes SEC EDGAR as the dataset. An agent can tell what this tool does without opening the schema, and the scope is explicitly limited to 'Listed companies only (CIKs in the SEC ticker list; no individuals)'.

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 clear usage context: use a ticker or CIK, filter by form types and date, and note that 'Documents are linked, not read'. The exclusions are also useful, because individuals and non-listed companies are not eligible. It also points to 'try_free' as a free alternative. However, no sibling tools are explicitly named as alternatives for overlapping needs.

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

All Lordevo Shop (x402 website checks) tools Inspect

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

Need Help?