Skip to main content
Glama

get_item_event_signal

Read-onlyIdempotent

특정 품목의 명절·김장 이벤트 신호를 반환한다. signal_type=price(가격급등 선매입) 또는 demand(가격하락 매수적기).

order_plan_suggestion 은 방식 A '제안형' — 기존 suggest_order_plan (POST /api/predictive-orders/suggest-trigger) 호출용 payload 를 생성만 하며, AI 는 발주를 실행하지 않는다(사람 승인 게이트, 특허 정합).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item": "<item>"
    },
    "name": "get_item_event_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes품목 한글명. 예: 사과, 대파, 배추, 생고추

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses a key behavioral trait: the order_plan_suggestion is proposal-only, the AI does not execute procurement, and a human approval gate applies. That is genuine value-add for an agent deciding what to do with the output; only rate limits or freshness of signals are unaddressed.

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?

Two short blocks: what is returned first, then the behavioral caveat about the suggestion payload. Efficient and front-loaded, though the suggest_order_plan endpoint path is detail the agent rarely needs.

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

Completeness5/5

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

An output schema exists, so return values need no prose, and annotations already cover the safety profile. The description fills the remaining gap — that the tool produces a proposal rather than an executed order — leaving nothing essential an agent needs before calling it.

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 description adds nothing about the single 'item' parameter — the Korean-item example is already in the schema. Baseline 3 applies since the schema fully carries parameter meaning.

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 states a specific verb and resource — returning holiday/kimjang event signals for a given item — and enumerates the two signal types (price surge pre-buy, demand drop buy timing). It does not explicitly differentiate from neighbors such as get_seasonal_pattern or decide_buy_or_wait, 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 Guidelines3/5

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

It explains what each signal_type means, which implies when the result is relevant, but never states when to call this instead of sibling decision tools. The suggest_order_plan mention describes a downstream payload field, not a when-to-use alternative, so guidance is implied rather than explicit.

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