Skip to main content
Glama
Sign In

Agent Data Tools

by io.github.Nutshell2000
OverviewDiscussionsAdmin

SEC filings: 10-K, 10-Q, 8-K by ticker

sec_edgar
Read-only

SEC filings of a US public company from EDGAR by ticker or CIK: the latest 10-K, 10-Q, 8-K, Form 4 and other forms with dates and document links, optionally one form type. Use to find a company's annual or quarterly report, insider trades or recent events. Example: ticker=AAPL. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key, e.g. 320193 (instead of ticker)
formNoOnly this form type, e.g. 10-K, 10-Q, 8-K or 4 (default: all)
limitNoFilings to return, 1-50 (default 10)
tickerNoStock ticker such as AAPL (or give cik)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, openWorldHint) and repeat-charging (idempotentHint=false), and the description correctly and consistently reinforces this with 'each call is charged, so repeats are not free.' It adds genuinely new operational context absent from structured fields: $0.002/call via x402 USDC or card key, first 25 free, failed calls free.

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?

Purpose and scope are front-loaded in the first sentence, followed by use cases and then commercial terms. The pricing sentence is dense but each clause (per-call price, payment paths, free tier, failed-call policy) carries distinct decision-relevant information for an agent.

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, the description appropriately sketches the return payload ('forms with dates and document links'), and all four parameters are schema-documented. Missing only finer return/pagination detail (e.g., ordering of results versus the limit parameter), which is a minor gap for this read-only lookup.

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 ticker, cik, form, and limit (1-50, default 10) are already documented in the schema. The description only adds 'optionally one form type' and an example (ticker=AAPL), which slightly clarify that filtering is optional but mostly restate the schema; 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?

States a specific verb+resource with scope: 'SEC filings of a US public company from EDGAR by ticker or CIK,' and enumerates the covered form types (10-K, 10-Q, 8-K, Form 4). It does not distinguish itself from related siblings such as sec_filings, sec_8k, or sec_insider, so the agent must infer the boundary.

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?

Gives concrete usage contexts: 'Use to find a company's annual or quarterly report, insider trades or recent events,' which maps intent to the covered form types. It offers no explicit when-not guidance or named alternative, leaving overlap with the more specialized sibling tools unresolved.

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

All Agent Data Tools toolsInspect
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