Skip to main content
Glama
Sign In
openmarkets

openmarkets

by danchev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_ttm_cash_flow_statement

Retrieve trailing twelve months cash flow statement entries for any stock ticker to analyze cash flow performance over the past year.

Instructions

Retrieve the trailing twelve months (TTM) cash flow statement for a given ticker.

Args: ticker (str): The symbol of the security.

Returns: list[TTMCashFlowStatementEntry]: List of TTM cash flow statement entries.

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_ttm_cash_flow_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but only states the basic operation. It does not disclose behaviors like data freshness, error handling, or any required permissions, leaving significant gaps for the agent.

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?

The description is extremely concise with two clear sections (Args, Returns). Each sentence is necessary and efficiently communicates purpose and parameter without superfluous text.

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 simple one-parameter tool with an output schema, the description covers the core functionality. However, it could mention that it returns a list of TTM cash flow entries, which is partially covered by the output schema. Lacks any mention of how it differs from similar tools like get_ttm_income_statement.

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?

The only parameter 'ticker' is described in the docstring as 'The symbol of the security', which adds minimal meaning beyond the schema's title 'Ticker'. Given 0% schema description coverage, this weak compensation keeps the score at baseline 3.

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?

The description clearly states the verb 'Retrieve' and the resource 'trailing twelve months (TTM) cash flow statement' for a given ticker. It distinguishes this tool from siblings like get_balance_sheet and get_income_statement by specifying TTM cash flow.

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?

No guidance is provided on when to use this tool versus alternatives, such as a standard cash flow statement or other financial statements. The description does not mention prerequisites or context for optimal use.

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