Skip to main content
Glama

FarmTempo

get_events_upcoming

Read-onlyIdempotent

오늘 기준 향후 horizon_days(기본 14일=D-14 경보) 내 도래하는 명절(설날·추석)과 김장철(11/1~12/15) 이벤트, 그리고 27년 실측 기반 영향 품목 신호를 반환한다.

각 품목 신호는 두 가지로 분리된다:

  • price: 명절/김장 가격급등 → 선매입(발주 권고 제안) 대상

  • demand: 수요폭증인데 가격하락(공급폭증) → '매수 적기' 플래그

강도(강/중/약)와 일관성(consistency %)을 함께 노출한다.

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

Input Schema

NameRequiredDescriptionDefault
horizon_daysNo조회 범위 일수 (기본 14=D-14 경보 윈도우, 최대 200=장기 카운트다운)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds real domain context beyond that: the semantics of each signal type, the strong/medium/weak intensity and consistency-percent fields, and the D-14 alert framing. It does not describe ordering or coverage limits of the returned set, but the output schema carries the return shape.

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 lead sentence front-loads the core behavior (what is returned and over what horizon), followed by a compact two-bullet breakdown of signal semantics. The structure is easy to scan, with only minor redundancy between the opening line and the bullet definitions.

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 single-parameter, read-only tool with full annotations and an output schema, the description supplies what structured fields cannot: what counts as an 'event' (holidays plus a hard-coded kimjang window) and how to interpret the two signal classes. Nothing essential for calling it correctly is missing.

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?

With one parameter at 100% schema coverage, the schema already documents horizon_days including its default and 200-day maximum. The description only restates the default as a 'D-14 alert window,' adding marginal domain framing rather than new 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 names a specific verb and resource: it returns upcoming holidays (Seollal/Chuseok) and kimjang-season (11/1~12/15) events within a horizon, plus per-item impact signals derived from 27 years of measured data. The scope is precise enough that an agent can tell it produces forward-looking calendar/signal data rather than historical prices. It stops short of differentiating itself from similar siblings such as get_item_event_signal or get_seasonal_pattern.

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?

Interpretation guidance is present and actionable: a 'price' signal means pre-buying/order recommendation, and a 'demand' signal means a buy-now flag despite falling prices. However, there is no explicit statement of when to call this instead of the sibling signal/seasonal tools, so the choice among alternatives is left to inference.

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