Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Historical prices (daily/weekly/monthly)

price_history
Read-onlyIdempotent

Retrieve historical OHLC, price changes, volume, value, frequency, and foreign buy/sell data for a stock symbol by day, week, or month, with date ranges defaulting to the past year.

Instructions

OHLC, change, volume, value, frequency and foreign buy/sell per day (or week/month) for one symbol. Dates default to the last year.

volume is lots; values IDR. Page through with page.

Returns (Stockbit's data field): data{result[{date, open, high, low, close, average, change, change_percentage, value (IDR), volume (LOTS), frequency, foreign_buy, foreign_sell, net_foreign (IDR)}], paginate{next_page}} newest first.

Endpoint: GET exodus /company-price-feed/historical/summary/{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": "price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoFollow paginate.next_page until it equals current page. Default 1.
limitNo12 in compact widget. Default 50.
periodNoperiod Default "HS_PERIOD_DAILY".
symbolYessymbol
end_dateNoLast date, YYYY-MM-DD. Default today.
start_dateNoFirst date, YYYY-MM-DD. Default one year ago.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive, so the description focuses on what annotations cannot say: units (volume in lots, value/net_foreign in IDR), newest-first ordering, pagination via paginate.next_page, and the default one-year window. That is genuine added context. It does not mention rate limits or data-delay/freshness, which keeps it from 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.

Conciseness4/5

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

Front-loaded with the payload contents, then units, paging, return shape and endpoint in a compact telegraphic style. Every line carries information. The terse field-list sentence is dense but readable rather than padded.

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 usefully enumerates the returned fields and their units, plus pagination mechanics, which is the main gap it needed to fill. For a simple read-only series tool with full schema coverage this is close to complete; only freshness/delay and rate-limit behavior are unstated.

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 symbol, page, limit, period and the date bounds. The description largely restates defaults already in the schema ('Dates default to the last year', 'Page through with page') and adds only the unit conventions, which apply to return fields rather than inputs. Baseline 3 is the right call.

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 exactly what the tool returns: OHLC, change, volume, value, frequency and foreign buy/sell for one symbol, at daily/weekly/monthly granularity, with an explicit endpoint path. An agent knows this is a historical price-series fetch. It does not contrast itself with the sibling price_daily_bars or price_performance, so it stops short of a 5.

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?

Operational hints exist (dates default to the last year, page through with page), but there is no when-to-use or when-not guidance and no alternative named among the many price_* siblings. The agent must infer that this is the multi-period historical series rather than the daily-bars or intraday variant.

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