Skip to main content
Glama

FarmTempo

usda_latest

Read-onlyIdempotent

시장·품목마다 가장 최근 리포트 날짜의 행만.

⛔ 최신 날짜는 시장마다·품목마다 다르다. 한 날짜로 뭉뚱그리지 말고 행마다 report_date 를 읽을 것. ⛔ 도시끼리 합치거나 평균 내지 않는다 — 각자의 시장이다.

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_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo시장×품목 한 조합당 행 수
marketNo터미널 시장 접두어: AJ, AS, BH, BP, CA, DU, HC, HX, MH, NA, NX
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.6/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 safety is covered; the description adds genuinely non-obvious behavior — that the latest date varies per market×commodity, that the caller must read report_date per row rather than assume a single date, and that city rows must not be merged or averaged. Those are the exact failure modes an agent would otherwise commit. It stops short of saying what happens when a market has no recent data.

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?

Three short lines, front-loaded with the scope statement, then two caution bullets. Little waste, though the first line and the first ⛔ partially restate the same per-market/per-commodity point. The description is also in Korean while tool names and sibling context are English, a minor consistency friction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, optional-only filter tool with annotations and no output schema, the description covers the core semantics of 'latest' and the no-aggregation rule. It omits what an empty result means, whether a market with stale data still returns rows, and any hint of the returned columns beyond report_date, leaving the agent to discover those at call time.

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%, including the important detail that limit means rows per market×commodity combination and that origin must match the published spelling exactly. The description contributes nothing about market, origin, commodity or limit, so the schema is doing all the work — baseline 3 applies. Without the schema text, the origin scoping note ("최신 날짜도 이 원산 안에서 잡는다") would be a meaningful addition.

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 states a precise scope: only rows from the most recent report date, defined per market and per commodity ("시장·품목마다 가장 최근 리포트 날짜의 행만"). That is specific enough that an agent can tell this apart from a general price-listing tool, but it never names the underlying resource (USDA terminal-market price reports) and does not differentiate it from the similarly named usda_sp_latest sibling.

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 only implied — the agent must infer 'call this when you want the freshest snapshot rather than a date range.' No alternative is named and no condition is given for choosing usda_prices or usda_sp_latest instead. The two ⛔ lines constrain how to interpret results, but they are cautions, not when-to-use 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