Skip to main content
Glama
toss-invest-mcp

toss-invest-mcp

by jihwan0102

market_hours_us

Read-only

Get US stock market session times in KST for previous, current, or next day, including day market, pre-market, regular, and after-hours.

Instructions

미국장 세션 시간(데이마켓/프리/정규/애프터, 전일·당일·익일). 모든 시간 KST.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful non-obvious behavior: all times are normalized to KST, and it discloses the full session set and day-offset coverage, which annotations cannot express.

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?

A single dense sentence with the resource and timezone constraint front-loaded and zero filler. The parenthetical enumeration is compact but slightly telegraphic (dot-separated abbreviations), which keeps it just short of ideal readability.

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?

For a read-only, zero-parameter lookup with an output schema, the description supplies the essentials: which sessions, which day offsets, and the timezone. Minor gaps remain around holiday/weekend behavior and disambiguation from kr_market, but nothing critical to correct invocation is missing.

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 the baseline is 4. The parenthetical list of session/d ay categories is not parameters but describes the response shape, which is already covered by the output schema; no parameter explanation is needed.

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 a specific resource (US market session times) and enumerates the exact session types returned (day/pre/regular/after-hours) plus the day offsets (previous/today/next). '미국장' implicitly separates it from the kr_market sibling, but the text never explicitly contrasts the two.

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 by the content: an agent can infer 'call this when you need US session boundaries.' There is no explicit when-to-use, when-not-to-use, or mention of kr_market as the alternative for Korean sessions, which is the most plausible sibling confusion for this tool.

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