Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

intraday_prices

Read-only

Fetch an IDX symbol's intraday minutely close-price series for building volume and price-move signals; returned points are ordered, not timestamped, so pair them with market session data for timing.

Instructions

Intraday minutely close-price series for a symbol (the basis for volume/price-move signals). ORDERED, NOT TIMESTAMPED. The row carries no clock reading this server recognises and none is computed, so prices[i] cannot be placed on a clock. IDX breaks midday (Mon-Thu 12:00-13:30 WIB, Fri 11:30-14:00 WIB), which means index x interval is NOT wall-clock time: two adjacent points can straddle a 90- or 150-minute gap. Any timing conclusion drawn from the index alone is unsound; market_session gives the clock. interval is what was ASKED FOR, not a measured spacing. A null in prices is a point the wire did not spell as a number — it is absent, not zero. unmapped.sampleKeys names the row's other keys, so a time channel under a different name would show up there. note carries the same warning for a caller reading the payload alone.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker
intervalNoMinutes per point (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already establish a safe read (readOnlyHint=true, destructiveHint=false), and the description adds substantial behavior beyond that: the series is ordered but not clock-stamped, index spacing is not wall-clock time due to the IDX midday break, `null` means absent not zero, and `interval` is requested rather than measured. This is exactly the kind of payload-shape context that prevents wrong conclusions downstream.

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 most important warning ('ORDERED, NOT TIMESTAMPED') is front-loaded immediately after the purpose clause, and each following sentence adds a distinct constraint rather than restating the schema. It is dense and slightly repetitive in the closing `note` sentence, but no sentence is truly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 full burden of explaining the response and does so: it names the fields (`prices`, `unmapped.sampleKeys`, `note`), explains null semantics, and warns about the ordering/time fallback. An agent has enough to call the tool and interpret its result without further context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds genuine meaning the schema does not: `interval` is what was asked for, not a measured spacing, which changes how an agent should interpret the data. `symbol` is left to the schema's 'IDX ticker' note, which is adequate.

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 first clause names a specific verb and resource: 'Intraday minutely close-price series for a symbol', with the parenthetical use case (basis for volume/price-move signals). It is identifiable as a raw price-series tool, but it never distinguishes itself from close siblings like chart_series, quote, or technicals, so the agent must infer the boundary.

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?

Useful routing is implied rather than stated: 'market_session gives the clock' points the agent at a sibling for timing, and the IDX midday-break explanation warns against index-based timing inferences. However, there is no explicit 'use this when / use X instead' guidance for the primary alternatives (chart_series, quote), so the agent must infer when this series is the right source.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.