Skip to main content
Glama

FarmTempo

market_get_item

Read-onlyIdempotent

품목 상세 — 시세 추이 + 평년 밴드 + 등급/등급사유.

⚠ B·C등급 응답에는 예측 필드가 없습니다(부재). A등급만 forecast_available=true이며 실제 3스케일 방향 예측·신뢰도는 기존 예측 파이프라인이 제공합니다. 반입량·법인집중도는 이번 범위 밖(원자료 확보 후 추가).

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_key": "<item_key>"
    },
    "name": "market_get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo최근 N일 시세 추이
item_keyYes

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 the read-only, idempotent, closed-world profile, so the description's added value is the grade-dependent response shape: B and C grades have forecast fields absent, while only A grade sets forecast_available=true and defers actual direction/confidence to the forecast pipeline. That is a genuinely useful behavioral disclosure beyond annotations, though it stops short of describing pagination or response envelope.

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 content block summary is front-loaded in a single line, followed by two focused caveats. The warning glyph and bolding make the grade constraint scannable, and no sentence is redundant, though the parenthetical asides are slightly verbose.

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 burden of describing returns, and it does so at the field-group level plus the critical grade-dependent absence of forecast fields. The missing piece is item_key semantics and any hint about response size or time span behavior for the default 365 days.

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 only 50%: 'days' is documented in the schema, but 'item_key' has no description anywhere. The description adds no meaning about item_key format or how days interacts with the normal-year band comparison, so it does not compensate for the coverage gap. Baseline 3 applies for a two-parameter tool with partial coverage.

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 (item detail) and enumerates the returned content blocks: price trend, normal-year band, and grade plus grade reason. It also scopes out arrival volume and corporate concentration, which helps distinguish it from data-bearing siblings. It does not name a specific alternative tool, but the resource-level purpose is unambiguous.

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 implied through the grade-dependent behavior: agents learn that only A-grade items carry forecast fields and that arrivals/concentration are not covered here. However, there is no explicit when-to-use / when-not-to-use statement pointing at siblings such as get_item_price_history or predict_demand_for_item, so the agent must infer routing.

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