Skip to main content
Glama

도매시장 휴장일 (Wholesale market calendar)

market_calendar
Read-onlyIdempotent

[B2AI] 도매시장 개장/휴장과 다음 개장일.

⛔ Phase 12a 의 판정 함수(receipt_price.market_status)를 그대로 쓴다. 영수증 시세 대조와 이 캘린더가 다른 답을 내면 안 된다.

OPEN=거래 있음 · MARKET_CLOSED=휴장(수집됐으나 거래 0건) · NO_DATA=미수집. 휴장과 미수집을 뭉뚱그리지 않는다.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD (생략 시 오늘)
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the status vocabulary: OPEN means trades occurred, MARKET_CLOSED means collected-but-zero-trades, NO_DATA means not collected, with an explicit warning not to conflate the last two. That distinction is genuine behavioral context an agent cannot get from annotations. It stops short of describing the response shape or the guarantee about 'next opening day' when the market is open.

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?

Purpose is front-loaded and the status glossary is compact and high-value. However, the reference to an internal 'Phase 12a' determination function and the internal module path receipt_price.market_status is implementation jargon that consumes space without helping an agent decide or call correctly, and the emoji-blocked warning line is forceful but low-information.

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

Completeness3/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 must carry the return-value burden, and it partially does by defining the three status values and promising the next opening day. It omits how many entries the window returns, the ordering, the timezone/holiday source, and how statuses are presented across a multi-day range — gaps that matter for a 7-day-default calendar tool.

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

Parameters2/5

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

Schema description coverage is 50%: the date parameter carries a YYYY-MM-DD/default-today note, while the days parameter (default 7, range 1-31) has constraints but no explanation. The description adds nothing about either parameter — no clarification of whether days counts forward from date, whether weekends/holidays are skipped, or the timezone. For a two-parameter tool where half the schema is bare, the description should compensate and does not.

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 opening line states a concrete resource and output — wholesale market open/closed status plus the next opening day — which an agent can act on immediately. It does not explicitly distinguish itself from siblings such as get_wholesale_prices or compare_my_price_vs_wholesale, but the calendar framing is specific enough that confusion is unlikely.

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: the '⛔ receipt price comparison and this calendar must not give different answers' note hints that this tool should be consulted alongside price comparison, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer that this is a precondition check before interpreting price data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources