Skip to main content
Glama

FarmTempo

predict_demand_for_item

Read-onlyIdempotent

⚠️ 실제 매장 판매·주문 자료로 만든 예측이 아니라 규칙으로 만든 참고값입니다(method='rule-baseline-v1'). 사용자에게 수요 '예측'으로 말하지 말고 '규칙 기반 참고값'이라고 밝히세요. [AGENT_HONESTY 20261011]

품목별 일자 수요량을 마트 거래 단위와 kg 환산으로 동시 반환.

단위 정책

각 수량 필드는 trade_unit_value + trade_unit + kg_equivalent 3중 표현. 외부 AI는 kg_equivalent로 정규화 계산, 마트 UI는 trade_unit_value로 표시. 환산 출처: KAMIS·가락시장 관행 표준.

mart_id

현재 무시. 향후 매장별 모델 + 매장별 단위 환산 계수 오버라이드 예약 필드.

Returns per-day demand forecast in dual units (trade + kg). Method is rule-based heuristic; ML migration planned.

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_code": "<item_code>"
    },
    "name": "predict_demand_for_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
mart_idNo매장 식별자 (현재 무시, B2AI forward-compat)
item_codeYes품목 한글명. 예: 배추, 무, 양파, 대파, 마늘, 오이, 감자, 생고추, 토마토
horizon_daysNo예측 기간(일). 1~30

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?

Discloses the underlying method (method='rule-baseline-v1'), that mart_id is currently ignored, and the dual-unit representation policy, adding significant context beyond the readOnly/idempotent annotations. It does not mention rate limits or other operational constraints, but for a read-only tool this is largely sufficient.

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?

Uses headings and front-loads the honesty warning. The English summary partially duplicates earlier content, but overall the structure is clear and efficient.

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, so the description explains the return fields (trade_unit_value, trade_unit, kg_equivalent) and the method. It is largely complete for correct invocation, though it could specify the shape of the returned list of days.

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 the schema already documents all parameters. The description reiterates that mart_id is ignored and explains the unit policy, but adds little new meaning for item_code or horizon_days beyond what the schema provides.

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?

States it returns per-day demand in dual units (trade + kg) for an item, clearly a forecasting-like resource. However, it does not differentiate from sibling tools such as get_seasonal_pattern or get_item_event_signal that might also inform demand.

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?

Warns not to call it a 'forecast' but a 'rule-based reference', which is usage guidance for presentation. Yet it gives no explicit when-to-use guidance versus alternatives or when-not-to-use conditions.

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