Skip to main content
Glama

FarmTempo

mkt_check_delivery

Read-onlyIdempotent

공급자의 신고된 배송 조건으로 지정 시군구 커버 여부를 판정한다. status=SELF(자차)/CARRIER(외부 운송)/PICKUP_ONLY(산지 인도)/NEGOTIATE(미신고 — 결격 아님)/OUT_OF_RANGE(권역 밖·육로 미연결). unit_price_krw·qty_value·qty_unit 을 함께 주면 운임 포함 인도원가와 kg당 인도단가(원/kg)를 같이 계산한다. 좌표·읍면동·주소는 반환하지 않는다. 단위: distance_km_straight 는 킬로미터(km)이며 예상 직선거리입니다(도로거리·소요시간 아님). fee_estimate_krw 는 대한민국 원(KRW) 범위이고 정보가 부족하면 min·max 모두 null 입니다(0원 아님). max_load_kg 는 킬로그램(kg). 모든 배송 정보는 공급자 신고 기준이며 팜템포가 검증하지 않았습니다. 행정구역 경계: 통계청 SGIS(공공누리 제1유형) / 가공: vuski/admdongkor (CC BY 4.0)

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": {
      "supplier_id": "<supplier_id>",
      "region": "<region>"
    },
    "name": "mkt_check_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNo품목명 — kg 환산표 조회용
regionYes구매자 시군구 코드 5자리 또는 '경기 구리시'
qty_unitNokg/상자/망/단/포
order_krwNo주문 금액(대한민국 원)
qty_valueNo수량
supplier_idYes
unit_price_krwNo단가(원/단위)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: all delivery data is supplier-declared and unverified, coordinates/읍면동/addresses are deliberately not returned, distance is straight-line rather than road distance or travel time, and fee_estimate_krw is null (not 0) when data is insufficient. These are exactly the caveats an agent needs to interpret results correctly.

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?

Front-loaded with the decision the tool makes, followed by the optional cost computation, then unit/null-semantics caveats and provenance. Dense but every clause carries information; the SGIS/admdongkor license attribution at the end is the one element that serves compliance rather than tool selection.

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

Completeness5/5

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

There is no output schema, so the description carries the full burden and does so: it defines the status enum, the units and meaning of distance_km_straight, the min/max range semantics of fee_estimate_krw including the null case, and max_load_kg units. For a 7-parameter read-only tool this leaves no material gap.

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

Parameters4/5

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

Schema coverage is already 86%, so the baseline is 3; the description goes further by explaining the interaction between unit_price_krw, qty_value and qty_unit — that supplying them together triggers delivered-cost and per-kg calculation. It does not clarify region format (5-digit code vs. '경기 구리시') or item/order_krw roles, leaving those to the schema.

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

Purpose5/5

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

The first sentence gives a specific verb (판정한다 / determine coverage) and resource (supplier's declared delivery conditions vs. a given 시군구). It then enumerates the full status vocabulary (SELF/CARRIER/PICKUP_ONLY/NEGOTIATE/OUT_OF_RANGE) and adds a secondary capability (delivered cost and 원/kg calculation), so an agent knows exactly what the tool produces without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: call it with a supplier and buyer region to test coverage, and additionally pass unit_price_krw·qty_value·qty_unit when freight-inclusive cost is wanted. NEGOTIATE is explicitly flagged as '미신고 — 결격 아님', which is genuine decision guidance. It stops short of naming an alternative tool or stating when not to use it, so it is not a 5.

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