Skip to main content
Glama

Korea Travel Demand & Price Archive (요즘인기여행)

Daily values of one series (시계열 일별 값)

get_series_history
Read-onlyIdempotent

Daily observed values of one series_id for the last N days (archive starts 2026-10-14), with the 30-day summary. Compare only within the same series_id. 한 series_id 의 최근 N일 일별 관측값(아카이브 2026-10-14 부터)과 30일 요약.

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": {
      "series_id": "<series_id>"
    },
    "name": "get_series_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo기본 30
series_idYessearch_series 가 돌려준 series_id

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, non-destructive, closed-world, so safety is covered. The description adds behavior annotations don't: the archive boundary (2026-10-14), that a 30-day summary is bundled with the daily values, and the cross-series comparison restriction.

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?

Front-loaded with the core purpose and scope, and the constraint sentence is short and useful. The full English/Korean duplication doubles the length for the same content, which is the only structural waste.

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?

With no output schema, the description carries the return-value burden and does name the payload (daily values plus 30-day summary) and the data availability window. It omits ordering, pagination/truncation behavior at the 120-day cap, and error cases, but nothing essential to invoking 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?

Schema description coverage is 100%, so the schema already documents both parameters and the default (기본 30). The description only restates 'last N days', adding the archive floor but no format or unit details beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource: 'Daily observed values of one series_id for the last N days', plus what else comes back (the 30-day summary). An agent can tell this is a per-series time-series fetch rather than a search. It does not explicitly name the sibling it complements (search_series), so it stops short of 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?

Gives a real usage constraint ('Compare only within the same series_id') and the archive start date, which frames when data exists. However, it never says when to use this versus search_series or the other sibling tools, and the prerequisite that series_id must come from search_series lives only in the schema description.

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