Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Price line chart

price_chart
Read-onlyIdempotent

Retrieve a stock symbol's price line chart for timeframes from today to 5 years, including price points, percentage change, volume, and drawdown to analyze trend and performance.

Instructions

The price line of one symbol for a timeframe (today, 1w, 1m, 3m, ytd, 1y, 3y, 5y), as on the stock page.

Returns (Stockbit's data field): data{timeframe, xaxisopt 'intraday', chart_type PRICE_CHART_TYPE_LINE, allowed_chart_type[], interval_in_minutes, max_candles, previous, change, percentage, cagr, drawdown, line_weight, markingpoint, prices[{date (epoch ms string), formatted_date 'YYYY-MM-DD HH:mm:ss', xlabel, value, percentage, change, open, high, low, volume}], previous_timeframe_price{...}}.

Endpoint: GET exodus /charts/{symbol}/daily.

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

Input Schema

NameRequiredDescriptionDefault
toNoto
fromNoRange variant (getEmitenDailyChartByRange).
symbolYessymbol
intervalNoRange variant; only value seen.
timeframeNoMutually exclusive with from/to/interval variant. Default "today".
is_include_previous_historicalNoSent for ytd/1w (and porto IHSG 5y).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds real value by disclosing the full response payload (prices array fields, previous, change, percentage, cagr, drawdown, previous_timeframe_price) since no output schema exists, but it says nothing about permissions, rate limits, or pagination/candle caps behavior.

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 first sentence front-loads purpose and scope efficiently, and the endpoint line is compact and useful. The second sentence is a dense dump of return-shape notation that is hard to scan but earns its place given there is no output schema.

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 read-only chart tool with no output schema, the description supplies the return structure an agent would otherwise lack. The main gap is the undocumented range variant (from/to/interval) and the ambiguous is_include_previous_historical parameter, which the description never explains.

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%, so the baseline is 3; the description only restates the timeframe enum values that the schema already documents. It does not clarify the mutually exclusive from/to/interval variant, the is_include_previous_historical quirk, or how interval interacts with timeframe beyond what the schema says.

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?

Names a specific verb+resource (price line of one symbol) and enumerates the supported timeframes, which lets an agent distinguish it from intraday bar or history tools. It does not reference any sibling by name, so the differentiation from price_daily_bars or price_history is left implicit.

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?

The timeframe list implies the primary usage mode, but there is no explicit statement of when to prefer this tool over price_daily_bars, price_intraday_bars, or price_history, and no guidance on when to switch to the from/to range variant the schema hints at. An agent must infer selection criteria entirely.

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