Skip to main content
Glama

Income + balance + cashflow

fundamentals
Read-only

Income + balance + cashflow (GET https://app.deepvalues.ai/api/v1/fundamentals/{ticker}, e.g. https://app.deepvalues.ai/api/v1/fundamentals/AAPL — 0.001 credits per call ($0.005 when paid per call over x402); works with no credentials up to 25 call(s)/day per address) Missing data? Call request_data.

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": {
      "ticker": "<ticker>"
    },
    "name": "fundamentals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
periodNoannual
tickerYesThe real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ticker / description
      Added value: +"The real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses concrete operational facts: 0.001 credits per call, $0.005 under x402, and a 25 calls/day unauthenticated allowance per address. That is real cost and auth context an agent needs before calling; it omits any statement about response shape or how many periods the default limit returns.

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?

The purpose is front-loaded in the first three words, with endpoint, pricing, and auth quota packed into one parenthetical rather than sprawling prose. It is dense but every clause carries information; the sole redundancy is restating the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only fetch with no output schema, the definition covers access, cost, and a data-gap fallback, which is enough to invoke it safely. It still leaves the agent guessing about the returned statement structure and the semantics of period/limit, which matters for a tool whose whole value is the shape of the financial data returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: ticker is richly documented in the schema (including the BRK.B/BRK-B share-class note and path substitution), but period and limit receive no explanation anywhere. The description adds nothing about whether 'limit' counts statements or periods, or how annual vs quarterly changes the payload, leaving a meaningful ambiguity for a 3-parameter multi-statement tool.

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 the three statement types returned (income, balance, cashflow) and pins the exact resource via the endpoint URL with ticker substitution example, so an agent knows this is a per-company financial-statements fetch. It stops short of explicitly contrasting with siblings such as as_filed or company_overview, which also surface financial content.

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?

There is explicit routing for one case: 'Missing data? Call `request_data`', which is a genuine when-to-do-something-else instruction. However, there is no guidance on when to prefer this over as_filed, company_overview, or intrinsic_value, so the choice among overlapping financial tools is left to inference.

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