Skip to main content
Glama

FarmTempo

usda_sp_prices

Read-onlyIdempotent

보고된 대로의 산지 FOB 가격 구간. 값은 변형하지 않으며, 행마다 리포트 번호와 리포트 날짜가 붙는다.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
offsetNo
reportNo리포트: BR_FV110, IF_FV110, IF_FV130, IX_FV120, MB_FV110, OR_FV120, YA_FV110
commodityNo승인 범위: Apples, Chinese Cabbage, Onions, Dry, Potatoes, Tomatoes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds genuine value beyond that by stating values are raw/unmodified ('값은 변형하지 않으며') and that each row is tagged with report number and date. It omits pagination behavior (limit default 200, max 1000, offset) and how the from/to date bounds are applied.

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?

Two short clauses, front-loaded with the core statement of what the data is, then the fidelity caveat. No filler. Slightly under-specified rather than verbose, which is not a conciseness problem.

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

Completeness2/5

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

With six optional parameters, no output schema, and low schema coverage, the description should carry more weight. It helps by describing row contents (report number and date) in the absence of an output schema, but it leaves date-range filtering, pagination, and the default 200-row cap unexplained for a tool whose whole point is querying a price series.

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

Parameters2/5

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

Schema description coverage is only 33%, so the description needed to compensate and does not. It never explains the from/to date-range parameters, the limit/offset paging semantics, or how the 'report' codes (BR_FV110, IF_FV110, etc.) and approved commodity names interact with each other. The only indirect help is the note that rows carry report number/date, which loosely maps to two of the six parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says the tool returns shipping-point (산지) FOB price ranges as reported, with report number and date per row, which identifies the resource but not the action (list? query by date range?). It does not distinguish this tool from close siblings such as usda_sp_latest, usda_prices, or get_wholesale_prices, so an agent cannot tell which one to pick from the description 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 guidance and no exclusions. Nothing says whether this returns the full historical series versus a snapshot (as usda_sp_latest presumably does), nor when to prefer it over usda_prices. Usage must be inferred entirely from the tool name.

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