Skip to main content
Glama
Sign In

LastLook Data

by io.github.zev-lll
OverviewDiscussionsAdmin

Get Company Fundamentals (SEC EDGAR)

get_edgar_company
Read-onlyIdempotent

Returns financial fundamentals for any US public company from SEC EDGAR XBRL filings: revenue, net income, total assets, stockholders equity, and EPS. Includes both annual (10-K) and quarterly (10-Q) data for the most recent periods. Works for any ticker listed on a US exchange (AAPL, MSFT, TSLA, AMZN, NVDA, GOOGL, META, JPM, BAC, etc.). Source: SEC EDGAR. Price: $0.75 USDC per call via x402 (Base or Solana).

Input Schema

NameRequiredDescriptionDefault
tickerYesUS stock ticker, e.g. AAPL, MSFT, NVDA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol e.g. AAPL, MSFT, TSLA, AMZN, NVDA, GOOGL"New value: +"US stock ticker, e.g. AAPL, MSFT, NVDA"
    • changedInput schema / properties / ticker / maxLength
      Previous value: -5New value: +10
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "as_of": {
-      "description": "Date the data was fetched",
-      "type": "string"
-    },
-    "cik": {
-      "description": "SEC Central Index Key",
-      "type": "string"
-    },
-    "company_name": {
-      "description": "Company legal name",
-      "type": "string"
-    },
-    "edgar_url": {
-      "description": "EDGAR filing browser URL for this company",
-      "type": "string"
-    },
-    "fundamentals": {
-      "additionalProperties": {},
-      "description": "Financial data: revenue, net_income, total_assets, stockholders_equity, eps_basic",
-      "type": "object"
-    },
-    "ticker": {
-      "description": "Ticker symbol",
-      "type": "string"
-    }
-  },
-  "required": [
-    "ticker",
-    "company_name",
-    "cik",
-    "fundamentals",
-    "as_of",
-    "edgar_url"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, and the description usefully adds data coverage (annual 10-K plus quarterly 10-Q, most recent periods), the upstream source, and — critically — the per-call price of $0.75 USDC via x402 with payment networks. It does not disclose how many periods are returned or what happens for an invalid/unknown ticker.

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 purpose, metrics, and coverage before pricing. Slightly wasteful: two separate long lists of example tickers (AAPL/MSFT/TSLA/AMZN/NVDA/GOOGL/META/JPM/BAC, then AAPL/MSFT/NVDA) repeat information already in the schema.

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 description does the necessary work by naming the returned fields and the period types. Gaps remain on units/currency, number of periods returned, and ordering, but an agent can invoke the tool correctly.

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%, so the baseline is 3; the description earns extra by scoping the parameter to US-exchange-listed tickers and confirming the ASX-style free-text form. The example tickers largely duplicate the schema's own example, so the added value is modest.

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?

States a specific verb+resource ('Returns financial fundamentals ... from SEC EDGAR XBRL filings') and enumerates the exact metrics and filing types returned. No sibling tool covers company-level fundamentals, so it is unambiguously distinguishable.

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?

The domain constraint ('any ticker listed on a US exchange') implicitly excludes foreign/private companies, but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives. The agent must infer that this is the only fundamentals source among mostly macro/market-data siblings.

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

All LastLook Data 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