Agent Tools

sec_filings

Free tier: 25 calls/day per IP with header X-Free-Call: 1 (or ?free=1), then pay per call. Recent SEC EDGAR filings for a US-listed company by ticker or CIK: form type, filing and report dates, 8-K item codes with plain labels, accession number and direct document links. Filter by form (8-K, 10-K, 10-Q, 4, 13F-HR, comma list), since date and limit. Raw public data, not investment advice. Price $0.005 USDC per call via x402. Example output: {"company":{"name":"Apple Inc.","cik":"320193","tickers":["AAPL"],"exchanges":["Nasdaq"],"sic_description":"Electronic Computers","fiscal_year_end":"0926"},"filters":{"form":["8-K"],"since":null,"limit":3},"matched":12,"returned":1,"filings":[{"form":"8-K","amendment":false,"filing_date":"2026-07-31

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

Input Schema

Name	Required	Description
`cik`	No	Optional SEC CIK number, e.g. 320193
`form`	No	Optional form type or comma list, e.g. 8-K,10-Q
`free`	No	Use the shared free allowance (25 successful calls per IP per UTC day across eligible tools). Defaults to false.
`limit`	No	1 to 40, default 10
`since`	No	Optional earliest filing date, YYYY-MM-DD
`ticker`	No	Stock ticker, e.g. AAPL or BRK-B. Give ticker or cik

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / free

Added value: +{
+  "description": "Use the shared free allowance (25 successful calls per IP per UTC day across eligible tools). Defaults to false.",
+  "type": "boolean"
+}

AddedOct 28, 2026

TDQS

A3.6/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 so well: it discloses the free-tier limit (25 calls/day per IP), the mechanism (X-Free-Call: 1 header or ?free=1), the paid price ($0.005 USDC via x402), and the 'raw public data, not investment advice' caveat. It also sketches the response envelope (company, filters, matched, returned, filings). Gaps remain around error behavior for unknown tickers and what happens after the daily allowance is exhausted beyond 'pay per call'.

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 information is front-loaded and dense, but pricing is stated twice (free-tier line and 'Price $0.005 USDC per call via x402'), and the description ends mid-JSON with a truncated example output that adds length without being usable. That truncation is a structural defect rather than mere verbosity.

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

Completeness3/5

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

For a 6-parameter tool with no output schema and no annotations, the description covers cost, access mechanism, and query dimensions well, but the only return-value evidence is an example that is cut off partway through the filings array. Without an output schema, the agent cannot learn the full shape of a filing record or pagination semantics from the definition.

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; the description still adds value by explaining the free parameter's wire mechanism (header vs query flag) and by enumerating valid form values (8-K, 10-K, 10-Q, 4, 13F-HR, comma list). It does not restate the limit range (1-40, default 10) or the since format, but those are covered by the schema.

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?

The description states a concrete verb+resource: "Recent SEC EDGAR filings for a US-listed company by ticker or CIK", and enumerates the returned fields (form type, filing/report dates, 8-K item codes, accession number, document links). That is enough to tell it apart from retrieval-style tools, but it never names the obvious sibling sec_facts, leaving the agent to infer that this returns filing metadata rather than extracted financial facts.

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 is implied rather than stated: 'by ticker or CIK', 'Filter by form (8-K, 10-K, 10-Q, 4, 13F-HR, comma list), since date and limit' tells the agent what knobs exist but not when this tool is the right choice versus sec_facts or federal_register_search. No when-not guidance, no note on what happens when the ticker is not US-listed.

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

All Agent 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?