Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Key statistics

financial_keystats
Read-onlyIdempotent

Retrieve key financial statistics for a stock symbol, including valuation, profitability, solvency, growth, and dividend metrics current and per year.

Instructions

Key statistics of one symbol: valuation (PE, PBV, EV/EBITDA), per-share data, profitability (ROE, ROA, margins), solvency, growth, dividend — current and per year.

Returns (Stockbit's data field): data{info, stats{...}, closure_fin_items_results[{keystats_name, fin_name_results[{fitem{id, name, value}}]}], financial_year_parent{financial_year_groups, financial_year_groups_usd}, financial_report_currency, dividend_group{dividend_year_values}}. Section names: Current Valuation, Per Share, Solvency, Management Effectiveness, Income, Dividend, Dividend History, Profitability, ... (e.g. 'Current PE Ratio (TTM)', 'Current Price to Book Value', 'Return on Equity (TTM)', 'Debt to Equity Ratio (Quarter)', 'Dividend Yield').

Paywall: unknown.

Endpoint: GET exodus /keystats/ratio/v1/{symbol}.

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": {
      "symbol": "<symbol>"
    },
    "name": "financial_keystats"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker, e.g. BBCA
year_limitNoYears of history Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description stays consistent with them. Beyond that it adds genuinely useful operational context: the underlying endpoint path and an explicit (if unresolved) paywall note. It does not cover rate limits or data latency, which keeps it off a 5.

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

Conciseness3/5

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

The purpose sentence is front-loaded and well-formed, but the second paragraph is a long raw field-path dump (closure_fin_items_results[...]) that is dense and of mixed value to an agent. The endpoint line at the end is useful but would read better near the top.

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 the return-shape burden and does so by naming the top-level fields, the section labels, and example metric names. Combined with the explicitly stated unknown paywall status and the endpoint, an agent has enough to call and parse the response, though pricing/gating behavior remains unresolved.

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 description coverage is 100%, with 'symbol' documented as an IDX ticker (e.g. BBCA) and 'year_limit' as 'Years of history Default 10'. The description's 'current and per year' phrasing loosely supports the year_limit concept but adds no syntax or default behavior beyond the schema, so the baseline 3 applies.

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 gives a specific resource (key statistics for one symbol) and enumerates the categories returned: valuation (PE, PBV, EV/EBITDA), per-share, profitability, solvency, growth and dividend, current and historical. It is clear what data comes back, but it never distinguishes itself from the sibling financial_ratios or financial_comparison_metrics, which plausibly overlap.

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?

There is no when-to-use guidance and no exclusions: nothing says when to reach for this instead of financial_ratios, financial_statements or financial_comparison_metrics. The only usage signal is the implicit 'one symbol' scoping, so an agent must infer routing from sibling names alone.

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