Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get 10-Year Cash History

get_cash_history
Read-only

Retrieve up to 10 years of quarterly cash and cash equivalents for a company from SEC XBRL filings, returned oldest first in USD; an empty result means cash was not measured, not zero.

Instructions

Up to 10 years of quarterly cash and cash equivalents for a company, as reported in its SEC XBRL financial statements (data.sec.gov). Returns history: one point per period end {periodEnd, usd, formType, isAnnual}, oldest first. When a 10-K and a 10-Q cover the same date, the annual figure is kept. Works for any company that files XBRL financials with the SEC. Only figures reported in US dollars are included, so a filer that reports in another currency returns an empty history: an empty history means not measured, never zero cash.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g., "AAPL", "TSLA")

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.20.0
    • addedOutput schema / properties / data / additionalProperties
      Added value: +true
    • addedOutput schema / properties / data / properties
      Added value: +{
      +  "data": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "cik": {
      +        "description": "SEC Central Index Key of the filer",
      +        "type": [
      +          "string",
      +          "number"
      +        ]
      +      },
      +      "history": {
      +        "items": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "formType": {
      +              "description": "Form the figure was read from, e.g. 10-K, 10-Q",
      +              "type": "string"
      +            },
      +            "isAnnual": {
      +              "description": "True when the figure comes from an annual report",
      +              "type": "boolean"
      +            },
      +            "periodEnd": {
      +              "description": "Period-end date, YYYY-MM-DD",
      +              "type": "string"
      +            },
      +            "usd": {
      +              "description": "Cash and cash equivalents at period end, in US dollars",
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "periodEnd",
      +            "usd",
      +            "isAnnual"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "ticker": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "history"
      +    ],
      +    "type": "object"
      +  },
      +  "success": {
      +    "type": "boolean"
      +  }
      +}
    • addedOutput schema / properties / data / required
      Added value: +[
      +  "data"
      +]
    • addedOutput schema / properties / data / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "data"
      +]
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, yet the description still adds substantial behavior: quarterly granularity, oldest-first ordering, the 10-K-over-10-Q dedupe rule, the USD-only filter, and the critical 'empty history means not measured, never zero cash' semantics. These are non-obvious behaviors an agent could not infer from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the resource and scope, then return shape, then tie-breaking, then caveats. Every sentence adds a distinct constraint or semantic; nothing is repeated from the title or schema.

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?

A one-parameter tool whose output schema and annotations already exist, yet the description still covers granularity, ordering, dedupe, currency restriction, and empty-result meaning. Nothing an agent needs to call it correctly or interpret results is missing.

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 coverage is 100% and the single ticker parameter is already documented in the schema, so the description carries no additional parameter burden. It adds no meaning beyond the schema (no nuance on ticker format, exchange listing, or class), which matches the baseline 3 for high-coverage schemas.

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?

Specific verb and resource: 'Up to 10 years of quarterly cash and cash equivalents for a company' from SEC XBRL filings. The explicit temporal and quarterly framing lets an agent distinguish it from point-in-time siblings like get_cash_position without opening either schema.

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?

It states the applicability envelope ('Works for any company that files XBRL financials with the SEC') and explains what an empty result means, which implies when the tool is appropriate. However, it never names an alternative tool or states when to prefer a point-in-time cash tool over this historical series, so usage is inferred rather than guided.

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

Deploy Server

Other Tools