Skip to main content
Glama

FarmTempo

usda_sp_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_sp_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo리포트×품목 한 조합당 행 수
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

B3.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description nonetheless adds a non-obvious behavioral caveat that annotations cannot express, namely that 'latest' is per-report×commodity and may lag by months for seasonal origins.

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 sentences: the first states what is returned and the second front-loads the hazard with a warning marker. Nothing is wasted, though the extreme terseness leaves the dataset identity implicit.

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?

With no output schema, three optional parameters at full schema coverage, and no required inputs, the definition covers the core filter and the staleness risk. It stops short of describing what a row contains or what the 'sp' series represents, which an agent needs to confirm before relying on it.

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 100%, and the schema already documents limit, report, and commodity, so the baseline is 3. The phrase 'per report×commodity' reinforces that those two parameters define the grouping, but it adds no format or range detail beyond the schema.

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 names the operation concretely: return only rows at the most recent report date per report×commodity. However, it never states what dataset 'sp' designates or how it differs from close siblings like usda_latest or usda_sp_prices, so an agent must infer the distinction from the name alone.

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?

The warning gives real operational guidance: for out-of-season origins the 'latest' date may be months stale, so read report_date on each row rather than assuming freshness. It offers no explicit when-to-use versus alternatives or prerequisites, so the guidance is cautionary rather than 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