Skip to main content
Glama

FarmTempo

usda_prices

Read-onlyIdempotent

보고된 대로의 터미널시장 가격 구간 — 그날 아침 도매시장 첫 수취인(도매업자)의 판매가(USDA 조사). 값은 변형하지 않으며, 행마다 리포트 번호와 리포트 날짜가 붙는다.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
marketNo터미널 시장 접두어: AJ, AS, BH, BP, CA, DU, HC, HX, MH, NA, NX
offsetNo
originNo원산 — 발표된 표기 그대로 정확히 일치 (예: South Korea). 최신 날짜도 이 원산 안에서 잡는다
commodityNo승인 범위: Apple Pears, Apples, Chinese Cabbage, Onions, Dry, Potatoes, Tomatoes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real domain behavior on top: prices are reported as ranges, they represent the morning's first-receiver selling price, values are explicitly not transformed, and every row carries report number and date, giving provenance. It does not describe pagination or row cardinality beyond the implicit limit/offset in the schema.

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?

It is a single dense sentence, front-loaded with what the data is and followed by the two qualifiers that matter (values untouched, report provenance). No filler, though the em-dash stacking makes it read like a data dictionary entry rather than guidance.

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?

No output schema exists, and the description partially covers return shape by stating each row carries report number and date. For a filtered query tool the remaining gaps (fields per row, price units/package basis, default and maximum page size) are modest but real; the default limit of 200 and cap of 1000 live only in the schema.

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 coverage is 43%, and the description itself adds no parameter guidance at all. The four undocumented parameters (to, from, limit, offset) are conventional date bounds and pagination, and the domain-specific ones (market prefix codes, exact-match origin, commodity whitelist) are already described in the schema, so the practical gap is small — but the description does not compensate for the uncovered parameters as required at this coverage level.

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 concrete resource: reported terminal-market price ranges from the USDA survey, defined as the first receiver's (wholesaler's) selling price that morning, with report number and date attached to each row. That is specific enough to know what data comes back. It never differentiates itself from the sibling usda_sp_prices or get_wholesale_prices, so an agent cannot tell which of the price datasets to pick from 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, when-not-to-use, or alternative-tool guidance. The siblings usda_latest, usda_sp_prices, and get_wholesale_prices all overlap in domain, and nothing here says which to choose or what prerequisite (e.g. a known USDA commodity/origin) applies.

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