Skip to main content
Glama
ferinator

Bullrun

by ferinator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get financial history

get_financial_history
Read-only

Read historical financial statements for a Bullrun ticker to check growth/CAGR consistency, margins, leverage, and cash-flow quality; use annual/quarterly periods with currency details for comparison.

Instructions

Read historical financial statements for one exact Bullrun ticker, with growth/CAGR consistency checks first, then income, balance sheet, cash flow, per-share metrics, margins and source currency. Defaults to a five-fiscal-year window of annual rows; request years=1-15 and periodType=quarterly or both for more detail. Use for growth consistency, margins, leverage and cash-flow quality; read the period/currency coverage before comparing.

Input Schema

NameRequiredDescriptionDefault
yearsNoFiscal-year window counting backward from the latest available fiscal year. Default 5; request up to 15 for longer research.
tickerYesThe Bullrun ticker. Use the listing ticker returned by search_stocks. US/European examples: AAPL, BMW, NESN. Most Asian listings keep their exchange suffix (6324.T, 0700.HK); some use bare codes (005930). Native or suffixed forms resolve only when one listing matches; search by company name or ISIN if unsure.
periodTypeNoDefaults to annual statements with a growth summary. Choose quarterly or both for detailed period research. Annual rows use fiscalQuarter=0.annual
includeEmptyRowsNoInclude sparse rows that have no major income statement, balance sheet, cash-flow, or EPS values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.9.0
    • changedInput schema / properties / periodType / default
      Previous value: -"both"New value: +"annual"
    • changedInput schema / properties / periodType / description
      Previous value: -"Return annual rows, quarterly rows, or both. Annual rows use fiscalQuarter=0."New value: +"Defaults to annual statements with a growth summary. Choose quarterly or both for detailed period research. Annual rows use fiscalQuarter=0."
    • changedInput schema / properties / ticker / description
      Previous value: -"The Bullrun ticker. Bullrun tickers: US and most European listings use the plain local symbol (AAPL, BMW, NESN, ABBN); most Asian and Indian listings keep their exchange suffix (Tokyo 6324.T, Hong Kong 0700.HK, Shanghai 600519.SS, Shenzhen 000001.SZ, Taiwan 2330.TW, Korea 000100.KS, Singapore D05.SI, India RELIANCE.NS), but some Japanese and Korean large caps are plain codes (Toyota 7203, Samsung 005930). Either form is resolved automatically when exactly one listing matches; use search_stocks to find a ticker by company name or ISIN."New value: +"The Bullrun ticker. Use the listing ticker returned by search_stocks. US/European examples: AAPL, BMW, NESN. Most Asian listings keep their exchange suffix (6324.T, 0700.HK); some use bare codes (005930). Native or suffixed forms resolve only when one listing matches; search by company name or ISIN if unsure."
    • changedInput schema / properties / years / default
      Previous value: -10New value: +5
    • changedInput schema / properties / years / description
      Previous value: -"How many fiscal years of history to return, counting backward from the latest fiscal year available."New value: +"Fiscal-year window counting backward from the latest available fiscal year. Default 5; request up to 15 for longer research."
  2. Changed1 schema field changedv0.7.0
    • changedInput schema / properties / ticker / description
      Previous value: -"The ticker exactly as listed on Bullrun, e.g. \"AAPL\", \"ABBN.SW\", \"BMW.DE\"."New value: +"The Bullrun ticker. Bullrun tickers: US and most European listings use the plain local symbol (AAPL, BMW, NESN, ABBN); most Asian and Indian listings keep their exchange suffix (Tokyo 6324.T, Hong Kong 0700.HK, Shanghai 600519.SS, Shenzhen 000001.SZ, Taiwan 2330.TW, Korea 000100.KS, Singapore D05.SI, India RELIANCE.NS), but some Japanese and Korean large caps are plain codes (Toyota 7203, Samsung 005930). Either form is resolved automatically when exactly one listing matches; use search_stocks to find a ticker by company name or ISIN."
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral context beyond that: five-fiscal-year default, years range 1-15, periodType quarterly/both options, ordering of growth checks, and source-currency coverage caveat. Pagination and rate-limit behavior remain unstated.

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?

Two well-formed sentences, front-loaded with the primary action and scope, then defaults and usage. The dense list of statement areas is purposeful and no sentence is wasted.

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 carries more of the burden and does a solid job outlining the returned statement categories, defaults, period options, and currency coverage. Some response-shape details remain implicit, but an agent has enough to call it correctly.

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%, so the schema already documents all four parameters in detail. The description reinforces ticker exactness and mentions years=1-15 and periodType behavior, but it adds little semantic detail beyond the schema's own parameter descriptions.

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?

States a specific verb and resource ('Read historical financial statements') and adds scope: one exact Bullrun ticker, growth/CAGR checks, income, balance sheet, cash flow, per-share metrics, margins, and source currency. The purpose is clear, but it does not explicitly name or distinguish itself from close siblings such as get_stock_metrics or get_company_data_coverage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage guidance ('Use for growth consistency, margins, leverage and cash-flow quality') and a practical caveat to check period/currency coverage before comparing. It lacks explicit when-not-to-use guidance or named alternatives, so it falls short of the top score.

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