Skip to main content
Glama

이전 주문 재사용 미리보기 (쓰기 없음)

handam_public_preview_history
Read-onlyIdempotent

선택한 본인 이전 주문에서 현재 주문으로 옮길 항목(주문자 연락처·상품·용도·옵션·리본/카드 문구, 선택 시 주소)과 출처, 기존 값 유지 항목, 복사되지 않는 항목(날짜·시간·받는 분·호실·금액·결제·메모)을 보여 줍니다. sourceFingerprint를 적용에 전달하세요.

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": {
      "orderId": "<orderId>",
      "sourceOrderId": "<sourceOrderId>",
      "profileId": "<profileId>",
      "ownerCapability": "<ownerCapability>"
    },
    "name": "handam_public_preview_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes
overwriteNo고객이 이전 값으로 덮어쓰기를 명시적으로 수락한 경로만
profileIdYes첫 접수 응답의 profile.profileId (조회 키일 뿐 권한이 아님)
sourceOrderIdYes
includeAddressNo이전 배송 주소·장소를 제안에 포함(명시적 선택, 적용 후에도 미검증·재확인)
ownerCapabilityYes첫 접수 응답에 한 번만 제공된 소유자 확인값. 클라이언트가 안전하게 보관해야 하며 다른 사용자와 공유하면 안 됩니다.

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?

The annotations already state readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the description adds real value beyond them by listing what will NOT be copied (date, time, recipient, room, amount, payment, memo) and by warning that an included address stays unverified and must be re-confirmed even after apply. The remaining gap is that it never says what happens after the preview is generated, for example whether it expires or is single-use.

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?

There are two sentences: the first lists in-scope, retained and excluded items, and the second gives the next-step instruction. The main content is front-loaded with no filler. The field lists are dense, but each group carries information the agent needs.

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 has to explain the return value; it does so by describing the moved items and their source, the items that keep existing values, and the items that are excluded. It also covers the handoff to apply. What is missing is how long the preview stays valid and whether repeated calls with the same inputs yield the same result, despite the idempotentHint.

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 67%; the schema itself explains overwrite, profileId, includeAddress and ownerCapability. The description adds the important handoff detail that sourceFingerprint must be forwarded to apply, even though sourceFingerprint is not in the input schema. Beyond that, it adds no new meaning for orderId, sourceOrderId or overwrite.

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 uses a specific verb and resource: it shows exactly which fields move from a previous order into the current order, and it enumerates the field groups (contact, product, purpose, options, ribbon/card message, optional address). The title marks it as write-free (쓰기 없음), which separates it from the apply step, but the description never names the apply sibling tool outright; it only says to pass sourceFingerprint 'to apply' (적용에).

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?

Only one piece of usage guidance is given: hand sourceFingerprint to apply, which implies 'preview before applying'. The description never says when to call this instead of list_my_history or preview_confirmation, and it never says when not to call this tool, so the agent has to infer the sequencing.

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