Crypto, web, finance and app data tools

us_company_filings

Latest SEC EDGAR filings of a US-listed company by ticker with links, optionally filtered by form (10-K, 10-Q, 8-K, 4 for insider trades, 13F-HR, S-1). Use for recent disclosures or insider filings.

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>"
    },
    "name": "us_company_filings"
  }
}

Input Schema

Name	Required	Description	Default
`forms`	No
`limit`	No
`ticker`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses recency ordering ("Latest") and that results include links, and reads implicitly as a read-only public-data lookup, but it never states read-only-ness, result freshness/coverage limits, or how many filings come back by default.

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?

Two dense sentences with no filler, and the core action and source are front-loaded before the optional filter detail. It is close to optimally sized, with only the trailing usage sentence verging on optional.

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?

An output schema exists, so return field details are not needed here. For a simple retrieval tool the description covers source, key, filter, and intent, but silence on the limit parameter's role and on whether multiple form codes can be passed leaves small operational gaps.

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 description coverage is 0%, so the description must compensate. It does so well for two of three parameters: "by ticker" pins the required key, and the parenthetical 10-K/10-Q/8-K/form 4/13F-HR/S-1 list gives far more meaning than the bare string schema. The limit parameter and multi-form syntax (the schema allows a single string) are left unexplained.

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: retrieving the latest SEC EDGAR filings for a US-listed company keyed by ticker, with the optional form filter named. It does not explicitly contrast itself with the sibling us_company_fundamentals, so it falls short of the top mark despite being unambiguous.

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?

"Use for recent disclosures or insider filings" gives a usage context, but there is no when-not guidance and no named alternative (e.g., use us_company_fundamentals for financial statement data). The agent must infer the boundary with siblings.

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

All Crypto, web, finance and app data tools 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?