Skip to main content
Glama

FarmTempo

get_seasonal_pattern

Read-onlyIdempotent

품목별 12개월 평년 가격 흐름입니다. 월값 = 올해 그 달 평일마다 구한 KAMIS 평년(지난 5년 같은 시기 ±3일 평일 평균 중 최고·최저를 뺀 3년 평균)의 평균. 단위는 계열 unit(원/kg 또는 원/개). 평년이 잡힌 평일이 10일 미만인 달은 null. 품목 매핑은 승인된 별칭만 쓰고, C등급 계열은 내지 않습니다(available=false, reason). 매입 시점 권고가 아니라 지난 5년의 계절 흐름입니다.

12-month KAMIS 5-year normal (trimmed mean of 3 of 5 years) per item; low/high month of the normal.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already establish that this is a safe, idempotent, closed-world read, and the description still adds substantial behavior: the exact aggregation method, the unit basis of each series (KRW/kg or KRW/item), null months when fewer than 10 qualifying weekdays exist, restriction to approved item aliases only, and suppression of C-grade series via available=false with a reason.

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?

The Korean block is dense and front-loaded with the methodology, but the trailing English sentence largely restates the first line rather than adding the low/high-month detail promised in the header. The result is moderately redundant rather than wasteful.

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?

An output schema plus full annotations carry the return shape and safety profile, and the description fills in edge cases (null months, available=false with reason). The remaining gap is how the per-item scope is chosen with an empty parameter object.

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 zero parameters, the baseline is 4, but the description discusses per-item mapping and approved aliases in a way that suggests the caller selects an item, while the schema exposes no such input — leaving ambiguity about how the item scope is determined. That is a real semantic gap rather than an addition.

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 and scope: a 12-month per-item normal price curve built from KAMIS 5-year normals (trimmed mean of 3 of 5 years). It also says what the tool is not — 'not a purchase-timing recommendation, but the seasonal flow of the last 5 years' — which separates it in spirit from decide_buy_or_wait/decide_buy_plan without naming those siblings.

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 context is implied rather than stated: the 'not a buy-timing recommendation' clause tells the agent when this tool is the wrong choice, but there is no explicit 'use this when you need X' or a named alternative such as get_item_price_history for actual observed prices.

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