Skip to main content
Glama
Sign In

Stablecoin Gateways

by com.stablecoingateways
OverviewDiscussionsAdmin

SEC EDGAR Financials and Filings

sec_company_facts
Read-onlyIdempotent

SEC EDGAR company lookup by stock ticker or CIK: revenue, net income, assets, liabilities, equity, cash, EPS and shares from the latest 10-K/10-Q XBRL data, plus recent 10-K, 10-Q and 8-K filings with links, exchange, state of incorporation and industry (SIC). Use when you need a US public company's fundamentals, filings or identity. Signed receipt. Price: $0.003 per call via x402 (USDC on Base or XRP on XRPL). The response includes a provenance block (sg-provenance/1): each fact carries its source, source URL, retrieval time and limits; evidence only, no score, rating or verdict. Example arguments: {"ticker":"AAPL"}.

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

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key (digits); alternative to ticker
tickerNoUS stock ticker; give ticker or cik

Output Schema

NameRequiredDescriptionDefault
dataNoSEC EDGAR identity (CIK, tickers, exchange, SIC, state), latest annual and quarterly XBRL financials, recent filings with links
receiptNoEd25519-signed, hash-chained receipt; verify free with the verify_receipt tool or POST /v1/verify-receipt. New receipts carry a signed `evidence` object: service_version, data_timestamp, validation, terms_version, terms_hash, provenance_hash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / data / properties / provenance
      Added value: +{
+  "description": "The response includes a `provenance` block (sg-provenance/1): each fact carries its source, source URL, retrieval time and limits; evidence only, no score, rating or verdict."
+}
  2. Changed1 schema field changed
    • changedOutput schema / properties / receipt / description
      Previous value: -"Ed25519-signed, hash-chained receipt; verify free with the verify_receipt tool or POST /v1/verify-receipt"New value: +"Ed25519-signed, hash-chained receipt; verify free with the verify_receipt tool or POST /v1/verify-receipt. New receipts carry a signed `evidence` object: service_version, data_timestamp, validation, terms_version, terms_hash, provenance_hash."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Paid result: { data, receipt }. Unpaid calls return an x402 PaymentRequired object instead (isError: true).",
+  "properties": {
+    "data": {
+      "description": "SEC EDGAR identity (CIK, tickers, exchange, SIC, state), latest annual and quarterly XBRL financials, recent filings with links",
+      "properties": {
+        "cik": {},
+        "exchanges": {},
+        "fiscal_year_end": {},
+        "latest_annual": {},
+        "latest_balance": {},
+        "latest_quarter": {},
+        "name": {},
+        "recent_filings": {},
+        "retrieved_at": {},
+        "sic": {},
+        "sic_description": {},
+        "source": {},
+        "state_of_incorporation": {},
+        "tickers": {},
+        "xbrl_available": {}
+      }
+    },
+    "receipt": {
+      "description": "Ed25519-signed, hash-chained receipt; verify free with the verify_receipt tool or POST /v1/verify-receipt"
+    }
+  },
+  "type": "object"
+}
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say read-only, idempotent, open-world; the description adds substantive behavior the agent could not otherwise know: a signed receipt, a per-call price of $0.003 via x402 (USDC on Base or XRP on XRPL), and a `provenance` block (sg-provenance/1) where each fact carries source, URL, retrieval time and limits. It further clarifies the tool returns evidence only, with no score or verdict, which pre-empts misinterpretation of the output.

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 resource and returned fields, then usage trigger, then payment and provenance details, then the example. Every sentence carries information, though the pricing and provenance clauses make it denser than typical; nothing is clearly removable.

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?

An output schema exists, yet the description still usefully characterizes the provenance block and states the evidence-only posture. Combined with full parameter coverage and read-only annotations, an agent has everything needed to decide, call, and interpret results.

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% and both parameters are documented, so the baseline would be 3. The description adds a small but real clarification that lookup is by ticker OR CIK (important since neither parameter is required) and supplies a concrete example argument {"ticker":"AAPL"}, which reduces invocation ambiguity.

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?

Names a specific verb+resource (SEC EDGAR company lookup) and enumerates the exact data returned: revenue, net income, assets, liabilities, equity, cash, EPS, shares from 10-K/10-Q XBRL, plus filings, exchange, state of incorporation and SIC. An agent can distinguish this from every sibling, none of which covers SEC fundamentals or filings.

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?

Explicitly states the trigger: "Use when you need a US public company's fundamentals, filings or identity." It also constrains scope to US public companies, which implicitly excludes private/non-US entities. It stops short of naming alternatives (e.g. lei_lookup or counterparty_check) for entity identity or screening, so there is no exclusion guidance.

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

All Stablecoin Gateways 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