Skip to main content
Glama

SEC EDGAR fundamentals (30 sats L402 or $0.025 USDC x402)

get_stock_fundamentals
Read-only

SEC EDGAR company facts (revenue, net income, EPS, shares, cash, debt) and ticker-to-CIK mapping for one US ticker. Not endorsed by the SEC. Price: 30 sats (Lightning) or $0.025 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"stock_fundamentals","data":{"company":{"ticker":"NVDA","cik":"0001045810","name":"NVIDIA CORP"},"metrics":{"revenue":{"value":60922000000,"unit":"USD","end":"2025-01-26","form":"10-K"},"net_income":{"value":29760000000,"unit":"USD"},"eps":{"value":1.19,"unit":"USD / shares"}}},"metadata":{"cost_sats":30}} Pay: Call it, get HTTP 402 (or MCP payment_required) with a Lightning invoice and macaroon, pay the invoice, then retry with Authorization: L402 <macaroon>:<preimage>. Or pay in USDC on Base via x402: sign the 402's x402 requirement (PAYMENT-REQUIRED header, or accepts in the JSON body) and retry with the PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1) header; only a 200 is settled.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_stock_fundamentals"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesUS ticker. EDGAR accepts any symbol in the SEC company_tickers.json map (featured: SPY, QQQ, NVDA, TSLA, AAPL, MSFT, AMZN, META, GOOGL, AMD, AVGO, MU, PLTR, NBIS, CRWV, RKLB, INTC, ASTS, HIMS, TSM, SOFI, ORCL, HOOD, NFLX, SMCI, COIN, MSTR, IBIT, MARA, GME).
x402_paymentNoOptional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.
l402_credentialNoOptional L402 credential '<macaroon>:<preimage_hex>' (or 'L402 <macaroon>:<preimage>') from a paid invoice or an active subscription. Omit it to receive the Lightning invoice and macaroon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / x402_payment
      Added value: +{
      +  "description": "Optional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the paid-access model (30 sats Lightning L402 or $0.025 USDC x402 on Base), the exact 402 handshake, which headers to retry with (Authorization: L402, PAYMENT-SIGNATURE v2, X-PAYMENT v1), that only a 200 means settled, and a legal disclaimer of SEC endorsement. An agent knows cost, auth and failure semantics before calling.

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?

Purpose is front-loaded correctly, but the body is bloated: a full illustrative JSON payload plus a dense payment paragraph that repeats information already present in the title and in the parameter descriptions. The sample aids comprehension of the absent output schema, yet the section could be trimmed.

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 example response payload is genuinely useful and shows the company/metrics/metadata shape. Payment, auth and retry behavior are fully covered; minor gaps are freshness/caching and rate limits, which an agent might want for a paid per-call endpoint.

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 coverage is 100% and each parameter already carries a detailed description (ticker list, x402 payment payload, L402 credential). The prose restates the payment alternatives but adds no format or constraint detail the schema does not already supply, so baseline 3 is appropriate.

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 first sentence names a concrete resource (SEC EDGAR company facts), enumerates the metrics returned (revenue, net income, EPS, shares, cash, debt), adds ticker-to-CIK mapping, and bounds scope to 'one US ticker'. That is enough for an agent to distinguish it from a filings-retrieval tool, though it never explicitly contrasts itself with the sibling get_stock_filings.

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 by the metric list and the 'one US ticker' scope, and the payment procedure tells the agent exactly what to do on a 402. However, there is no explicit when-to-use/when-not-to-use statement or routing rule against alternatives such as get_stock_filings or get_market_insights.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources