Skip to main content
Glama

SEC XBRL Company Facts

sv_facts
Read-only

Public-domain standardized fundamentals from SEC XBRL companyfacts: revenues, net income, assets, liabilities, equity, EPS per CIK/ticker (companyfacts panel). Params: ticker, limit. Free with X-ORKID-API-Key or $0.01 USDC/call via x402.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows, default 100, cap 500
panelNoPanel to query (default first). Available: companyfacts
tickerNoTicker, e.g. "AAPL"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context that annotations cannot express: free access with an X-ORKID-API-Key, or $0.01 USDC per call via x402, which matters for an agent deciding whether and how to invoke it.

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?

Two dense sentences with the data content front-loaded and payment/auth terms trailing. Minor waste in the parenthetical '(companyfacts panel)' repeating the panel name and in the 'per CIK/ticker' phrasing, but nothing extraneous enough to trim.

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?

For a read-only, three-parameter query tool with no output schema, the description covers what data comes back (the listed fundamentals) and the access cost model. The main gap is the unseen panel enumeration and limit cap, which the schema already carries.

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, limit (default 100, cap 500), and panel are already documented. The description's 'Params: ticker, limit' omits panel entirely and is slightly at odds with the schema, but it partially compensates by noting the '(companyfacts panel)' context.

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 names a specific resource (SEC XBRL companyfacts) and enumerates the exact fundamentals returned (revenues, net income, assets, liabilities, equity, EPS), keyed by CIK/ticker. An agent can tell this is standardized fundamentals data rather than filing documents or sentiment data, though it never explicitly contrasts itself with siblings like sv_filings or sv_fsds.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives. Given a sibling set that includes sv_filings, sv_fsds, sv_fsds_bulk, and sv_filing_sentiment, an agent is left to infer on its own which of these to call for financial statement data.

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