Skip to main content
Glama
stockbit-mcp

stockbit-mcp

IHSG (composite) chart

price_ihsg_chart
Read-onlyIdempotent

Retrieve the Jakarta Composite Index (IHSG) line for a selected timeframe, including optional previous historical data, to analyze index price movements.

Instructions

The Jakarta Composite Index (IHSG) line for a timeframe.

Returns (Stockbit's data field): Same as get_daily_chart.

Endpoint: GET exodus /charts/ihsg/daily.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "price_ihsg_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeframeNoPorto-performance hard-codes 5y. Default "5y".
is_include_previous_historicalNois_include_previous_historical Default "1".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only an endpoint path and a return pointer, which is modest added context. It says nothing about data freshness, caching, or trading-hours behavior for a market-data endpoint where that would matter.

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 efficient. However, 'Returns (Stockbit's data field): Same as get_daily_chart' is a dangling reference to a tool not in the sibling set, consuming a line without conveying usable information, and the raw endpoint string is developer-facing noise.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining the return value, and it defers entirely to an unspecified get_daily_chart. For a chart tool with enum timeframes and an ambiguous is_include_previous_historical flag, an agent is left without a usable picture of the response shape.

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% and the timeframe enum is fully enumerated in the schema, so the description need not repeat it. It does confirm the timeframe is the scoping dimension, but adds no meaning about granularity (e.g. what 'today' returns intraday vs. close) or what is_include_previous_historical actually changes.

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 a specific resource with a scope qualifier: 'The Jakarta Composite Index (IHSG) line for a timeframe.' An agent can tell this returns an index chart rather than a single-stock chart. It does not name or contrast the sibling price_chart, so differentiation is implicit rather than explicit.

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?

No when-to-use or when-not-to-use guidance is given. The agent must infer from the phrase 'IHSG' that this is for the composite index rather than an individual ticker, and there is no mention of how this relates to price_chart or get_daily_chart.

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