Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

company

[$0.001] Look up public company financials, CIK, recent SEC EDGAR filings (10-K/10-Q/8-K), and recent news sentiment by stock ticker (supports up to 5 batched tickers).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (default 50, max 500)
fieldsNoReturn only these result keys, e.g. ["ticker","company_name","recent_filings"]
tickerNoAny SEC-registered stock ticker (e.g., AAPL, COST, WMT, NVDA). Unknown tickers return 404 and are not charged.
tickersNoBatch: array of up to 5 tickers; priced unit price x count
include_newsNoInclude recent news headlines with sentiment for the company

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the $0.001 price tag, the 5-ticker batch cap, and the data classes returned, which is real added context. It omits authentication or rate-limit expectations and does not state what a batch response looks like or how partial failures in a batch are handled. Mutation risk is nil for a lookup tool, so the gaps are moderate rather than severe.

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?

A single front-loaded sentence with no filler: verb, resource list, and pricing all in one pass. The leading '[$0.001]' cost marker is compact and useful, though the parenthetical batch note slightly crowds the capability list. Nothing is redundant or padded.

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 100% schema coverage and no output schema, the description does enough: it enumerates the data classes returned and the pricing/batching model an agent needs before spending money. Missing is any statement of the effective input requirement (at least one ticker) and any hint at response shape for batched calls. Those are refinements, not blockers.

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 all five parameters (limit, fields, ticker, tickers, include_news) are already documented in the schema, and the description only restates the ticker and batch-cap semantics. It adds no meaning for 'fields', 'limit', or 'include_news' beyond what the schema says. Baseline 3 is the correct ceiling here.

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 specific resources: public company financials, CIK, recent SEC EDGAR filings (10-K/10-Q/8-K), and news sentiment, keyed by stock ticker. That is far more precise than the vague tool name 'company' and lets an agent tell it apart from most siblings. It stops short of a 5 because the overlapping 'news' sibling is never acknowledged, leaving ambiguity about which to pick for news-only queries.

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 only implied: the phrase 'by stock ticker' signals the input shape, and the mention of batched tickers hints at multi-company lookups. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives like news or company_compare. Nor does it clarify that a lookup with neither 'ticker' nor 'tickers' is effectively pointless, which matters since zero parameters are required.

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