Skip to main content
Glama

FarmTempo

get_auction_price

Read-onlyIdempotent

특정 품목의 경락(낙찰) 요약을 반환한다. 단위는 원/kg(거래중량 가중평균).

  • market 지정: 해당 시장 1곳의 평균 낙찰가·총물량·거래건수·가격범위 + KAMIS 정산 도매가 비교(기준 상이: 경락=낙찰가, KAMIS=정산 도매가).

  • market 생략: 전 시장을 평균가 오름차순(어디가 싼지)으로 반환.

  • date 생략: 최신 수집일 자동.

  • market 매칭: 코드(110001)·한글명(서울가락)·부분일치(가락) 모두 허용. 부분일치 복수 시 후보 목록 반환.

  • 미존재 품목·시장·날짜는 404 아닌 200 + {found:false, hint}.

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": "<item>"
    },
    "name": "get_auction_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo거래정산일 YYYY-MM-DD. 생략 시 최신 수집일.
itemYes품목 한글명. 예: 양파, 마늘, 배추, 사과, 복숭아
marketNo도매시장 코드(110001)·한글명(서울가락)·부분일치(가락). 생략 시 전 시장.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is lighter. It still adds real value by disclosing the weighted-average unit, the comparison baseline difference between 경락 and KAMIS, and that misses return 200 + {found:false, hint} rather than 404. However, since an output schema exists, the return-shape disclosure overlaps structured data and deeper traits (rate limits, empty-data handling beyond found:false) are absent.

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 one-line summary followed by tight bullets, one per behavioral branch, with no filler. A small amount of space is spent restating market-matching rules that already live in the schema descriptions.

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 rich annotations, full schema coverage, and an output schema, the description covers what an agent needs: default behaviors, matching semantics, sort order, and the non-error miss response. Minor gaps remain around how the KAMIS comparison is presented when data is unavailable, but nothing required for a correct call 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 date format, item examples, and market code/name/partial-match rules; the description largely restates these. The one genuinely additive detail is that a partial match hitting multiple markets returns a candidate list instead of guessing. That is useful but the baseline of 3 is right given how much the schema already carries.

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 first sentence states a specific verb and resource ('경락(낙찰) 요약을 반환한다') and pins down the unit and aggregation method (원/kg, 거래중량 가중평균), so the agent knows exactly what number it is getting. It also implicitly separates auction settlement price from KAMIS 정산 도매가, which helps distinguish it from wholesale-price siblings. It stops short of naming which sibling to use instead, which keeps it at 4.

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

Usage Guidelines4/5

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

Branches are spelled out: supplying market yields a single-market summary plus KAMIS comparison, omitting market returns all markets sorted ascending by average price, omitting date uses the latest collection date. This is clear when-to-use context for each parameter combination. It does not name alternative tools (e.g., for historical trends), so it is not a full 5.

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