Skip to main content
Glama

Tollkit

by io.github.UltraStarz
OverviewDiscussionsAdmin

SEC company profile and filings

sec_company
Read-only

Look up a US public company in SEC EDGAR by ticker or CIK: legal name, exchange, industry, state, fiscal year end, and its latest filings (10-K, 10-Q, 8-K, insider Form 4 and more) with direct links. Filter by form type, e.g. only 10-Ks.

$0.002 USDC per call over x402. Failed calls cost nothing. Call without payment to get a quote. The first 3 calls a day through this tool server are free (no wallet needed).

When to use: You need who a US public company is, or links to its recent filings. Use instead: sec_financials for the numbers; company_snapshot for profile plus numbers; company_due_diligence for ratios and 8-K summaries. Parameters: ticker or cik (one is required). form: only this form type, e.g. 10-K, 10-Q, 8-K or 4. limit: 1-40 filings, default 10. Returns: name, CIK, exchange, industry, state, fiscal year end, and filings[] with form, date and link.

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key, e.g. 320193. Give this or ticker.
formNoOnly this form type, e.g. "10-K".
limitNoHow many filings, 1-40 (default 10).
tickerNoUS stock ticker, e.g. "AAPL". Give this or cik.
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cik / description
      Added value: +"SEC Central Index Key, e.g. 320193. Give this or ticker."
    • addedInput schema / properties / limit / description
      Added value: +"How many filings, 1-40 (default 10)."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the x402 pricing model ($0.002 USDC per call), that failed calls are free, the quote-then-pay flow via the payment parameter, and a free daily-tier limit. These are operational facts an agent cannot get from annotations or schema alone.

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?

Front-loaded with the core purpose, then clearly sectioned into pricing, when-to-use, alternatives, parameters, and returns. Slightly repetitive restating parameters already in the schema, but no filler sentences.

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?

With no output schema, the description fully covers the return shape (fields and filings[] with form/date/link), the payment prerequisite, and the ticker-or-CIK input requirement. An agent has everything needed to call it correctly.

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 five parameters including the payment quote flow. The description adds only example form values (10-K, 10-Q, 8-K, 4) and restates the limit range, which is marginal added value; baseline 3 applies.

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?

Specific verb+resource: 'Look up a US public company in SEC EDGAR by ticker or CIK' with an enumeration of exactly what is returned (name, exchange, industry, state, FY end, filings with links). It explicitly differentiates itself from the three sibling SEC/company tools, so an agent can pick it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Contains explicit 'When to use' and 'Use instead' lines naming the exact alternatives (sec_financials for numbers, company_snapshot for profile+numbers, company_due_diligence for ratios and 8-K summaries). Routing is unambiguous.

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

All Tollkit 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