Skip to main content
Glama

FarmTempo

decide_buy_plan

Read-onlyIdempotent

aT 도매 정산가 기준 26품목. 필요량(kg)과 기한(오늘~7일)을 주면 세 가지 사는 방법의 예상 금액(중앙값·80% 범위, 신선도 손실 가정 포함)과 묶음별 과거 성적(과거 자료 검증·가상 구매 계산: 평균 절감·나쁜 5% 날·손해 본 날 비율)을 줍니다. 팜템포는 고르거나 주문하지 않습니다. 금액은 예측 기반 예시이며 약속이 아님을 사용자에게 밝히세요.

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>",
      "qty": "<qty>"
    },
    "name": "decide_buy_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyYes필요량(kg)
daysNo며칠 안에 필요한가(0=오늘, 최대 7 · 저장성 9품목은 14)
itemYes품목명 (예: 상추) — aT 기준판 26품목
weeklyNo매주 같은 양이 필요하면 true — 저장성 품목에 '다음 주 몫 미리 사기' 안을 함께 냄
loss_rateNo하루 신선도 손실 가정(예: 0.015). 없으면 묶음 기본값

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description usefully adds that no selection or ordering occurs and that all figures are prediction-based examples rather than commitments. That uncertainty caveat is real behavioral context not captured by any structured field. It stops at 4 because nothing is said about latency, data vintage, or what happens for items outside the 26-item set.

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?

Four sentences that front-load the scope, then the input-to-output mapping, then the no-order boundary, then the disclosure instruction. Dense but each sentence carries weight. The nested parenthetical describing the historical statistics is slightly run-on but still parseable.

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 no output schema, the description does the work of explaining the return value: three method estimates with median and 80% range, plus per-bundle savings, worst-5%-day and loss-day-ratio figures. Combined with full schema coverage and strong annotations, an agent has enough to call this correctly. Minor gaps are behavior for out-of-scope items and the output container format.

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 all five parameters (qty, days, item, weekly, loss_rate) are already documented in the schema. The description reinforces the quantity and deadline semantics and the 26-item domain constraint, but adds no syntax or edge-case detail beyond what the schema states, so the baseline 3 applies.

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 specific verb and resource: given required kg and a deadline it returns estimated costs for three purchase methods plus per-bundle historical performance, scoped to the 26 aT wholesale settlement-price items. That is far more informative than the name alone. It falls short of a 5 only because it never distinguishes itself from the similar sibling decide_buy_or_wait.

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 implied by the input framing ('give quantity and a deadline of today through 7 days') and by the scope boundary that it never selects or orders. However, there is no explicit when-to-use versus when-not guidance and no mention of decide_buy_or_wait or the margin/price siblings, so an agent must infer the routing decision.

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