Skip to main content
Glama

FarmTempo

market_list_items

Read-onlyIdempotent

전품목 시세 목록. 등급·표기명·최근 시세·전일비·평년비.

A등급=검증된 예측 계열(예측 제공), B등급=시세 상세, C등급=시세 조회. 단가는 KAMIS 도매·상품 정규화가(원/단위, KRW). 반입량 미포함(이번 범위).

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

Input Schema

NameRequiredDescriptionDefault
qNo품목명 검색
sortNochange|vs_normal|namechange
buryuNo부류 필터(이번 범위: 미설정)
gradeNoA|B|C 필터

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 establish readOnly/idempotent/non-destructive/local, so the description is free to add real context and does: unit and currency (KRW per unit), the KAMIS wholesale normalized-price source, and a scope exclusion (arrival volume not included in this range). Those are exactly the operational caveats annotations cannot express; it stops short of describing result count, pagination, or ordering behavior despite exposing a `sort` parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely compact, front-loaded with purpose, then grade legend, then unit/source, then scope caveat — each fragment carries distinct information with no filler. The telegraphic style is dense but each sentence earns its place.

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 properly compensates by listing the returned fields, and it covers units, source, and an out-of-scope caveat for a 4-optional-parameter read tool. What is missing is any indication of result volume/pagination and how results relate to the other price-retrieval tools in the catalog.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns above baseline by defining what the A/B/C grade filter actually selects (A = verified forecast series with forecasts, B = detailed price, C = plain price lookup). That is meaning not present in the schema's bare "A|B|C 필터", and it helps the agent choose a filter value.

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 opens with a specific verb+resource ("전품목 시세 목록" – list of all-item market prices) and immediately enumerates the returned fields (grade, display name, latest price, day-over-day change, year-average ratio). It never distinguishes itself from plausible siblings such as market_get_item, items_list, market_ticker, or get_wholesale_prices, so an agent cannot route between them from this text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative, even though the sibling list contains several overlapping price tools. The only orienting information is the meaning of grades A/B/C, which is parameter semantics rather than invocation guidance.

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