Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Latest prices of symbols

price_latest
Read-onlyIdempotent

Retrieve current OHLC, previous close, change, average price, volume, value, and frequency for one or more IDX symbols, stamped with the time of the last update.

Instructions

Latest OHLC, previous close, change, average price, volume, value and frequency of one or more symbols, stamped with the time of the last update.

Every number comes as {raw:{value}, formatted} with value a string. Prices and value are IDR.

Returns (Stockbit's data field): data[{symbol, company_id, datetime, open, high, low, lastprice, previous, change, percentage_change, value, volume, average, frequency}], each number as {raw{value (string)}, formatted}

Endpoint: GET exodus /company-price-feed/v3/prices/latest.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX tickers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description adds genuinely new behavioral context by disclosing the response envelope (data[...] with named fields), that every number is wrapped as {raw:{value}, formatted} with string values, and that prices/value are in IDR. It stops short of covering rate limits, symbol-count limits, or behavior when a symbol is unknown.

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 is well front-loaded with the payload contents, and the structure separates units, return shape and endpoint cleanly. There is some redundancy: the '{raw:{value}, formatted}' convention is stated twice (once generally, once inline in the Returns list), and the raw endpoint path is arguably scaffolding noise.

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-value burden and does so thoroughly by enumerating the response fields, their nesting, and their unit conventions. It is close to complete for a one-parameter read tool; missing only edge-case behavior (invalid tickers, partial results, symbol cap) that an agent might want before calling.

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% and the single 'symbol' parameter is documented in the schema as IDX tickers with a 1-100 item range. The description only adds the plural phrasing 'one or more symbols', which confirms multi-symbol batching but adds no format or syntax detail 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 names the resource precisely (latest OHLC, previous close, change, average, volume, value, frequency for one or more symbols) and states the scope ('stamped with the time of the last update'), so an agent can tell this is a current-quote fetch rather than a historical series. It does not explicitly differentiate itself from siblings like price_snapshot or price_history, which keeps it 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 Guidelines3/5

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

Usage is only implied: the word 'Latest' plus 'time of the last update' suggests current-quote retrieval, but there is no explicit statement of when to choose this over price_history, price_daily_bars, or price_snapshot, and no exclusions or prerequisites. An agent must infer the selection rule from the tool name and the word 'latest'.

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