Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Market open/closed

market_status
Read-onlyIdempotent

Check if IDX is open and how much trading time remains for regular and FCA sessions before making market decisions.

Instructions

Whether IDX is open now and the trading time left.

Returns (Stockbit's data field): {message, data:{market:{status (STATUS_OPEN|STATUS_CLOSE|...)}, iepiev_regular:{status}, iepiev_fca:{status}}}

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

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

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, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the data source (Stockbit's data field), the exact response envelope, and the backing endpoint. It could go further by noting freshness/rate-limit behavior for a live market-time poll, which is why it is not 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?

The first line front-loads the core answer, followed by return shape and endpoint. It is short and every line carries information, though the inline brace-notation return sketch is dense and slightly harder to parse than a short bullet list would be.

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 documents the returned fields (status, iepiev_regular, iepiev_fca). The status enum is left truncated as 'STATUS_OPEN|STATUS_CLOSE|...', so the full set of possible states remains unknown, which is the main remaining gap for a zero-parameter read.

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 there is nothing for the description to disambiguate and the baseline is a 4. Nothing in the text misdescribes the (empty) input surface.

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 gives a specific verb-and-resource statement: it reports whether IDX is open right now plus the trading time remaining. That is far more concrete than the bare title 'Market open/closed'. It does not distinguish itself from similarly named siblings such as market_session or session_status, 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?

There is no explicit when-to-use guidance, no when-not-to-use, and no pointer to an alternative tool. The only implied context is 'now', which tells an agent it is a real-time check but not how it relates to other market/session tools.

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