Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Market sessions

market_session
Read-onlyIdempotent

Retrieve today's IDX market session schedule, including pre-opening, trading sessions, breaks, and closing states with start/end times and time remaining.

Instructions

Today's IDX session schedule (pre-opening, session 1, break, session 2, pre-closing, post-trading).

Returns (Stockbit's data field): data{datetime 'YYYY-MM-DD HH:mm:ss' (WIB), detail{regular, fca}{session, state_name STATE_NAME_{PRE_OPENING,SESSION_1..5,BREAK,PRE_CLOSING,POST_CLOSING,MARKET_CLOSED}, is_last_session, is_end_of_day, state_start_time, state_end_time, time_left{raw seconds, formatted (Indonesian)}, suspend_info}}. UI: open = PRE_OPENING..POST_CLOSING, break = BREAK.

Endpoint: GET exodus /company-price-feed/market-time/session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered; the description adds the underlying data source (Stockbit), the actual endpoint (GET exodus /company-price-feed/market-time/session), the WIB timezone, and a UI rule mapping open to PRE_OPENING..POST_CLOSING and break to BREAK. That is meaningful behavior beyond the annotations. Minor gaps remain, such as what happens outside trading days, but the disclosure is well above baseline.

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?

Purpose is front-loaded in the first line, followed by a structured return-shape block and the endpoint. The dense field enumeration is justified because no output schema exists, though the nested brace notation (e.g. 'detail{regular, fca}') is somewhat hard to parse.

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 input parameters, no output schema, and a simple read-only operation, the description carries the return-value burden and does so thoroughly, including state names, time_left formatting, and suspend_info. The only real omission is usage context relative to sibling market-status tools.

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?

The tool takes zero parameters, so per the baseline there is nothing to disambiguate and no schema semantics to compensate for. The description correctly focuses its effort on return values instead.

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 opens with a specific resource and scope: 'Today's IDX session schedule' and enumerates the phases it covers (pre-opening, session 1, break, session 2, pre-closing, post-trading). That is more than a restatement of the title. It does not, however, distinguish this tool from siblings such as session_status or market_status, so an 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 Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative-naming guidance. 'Today's' implies a daily-schedule scope, but nothing tells an agent why it should pick this over session_status or market_status, and there are no stated prerequisites or exclusions.

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