Skip to main content
Glama

선택한 이전 주문을 현재 주문에 적용

handam_public_apply_history
Idempotent

고객이 미리보기를 확인한 뒤에만 호출합니다. 비어 있는 항목만 채우고(기존 값 우선) overwrite에 명시한 경로만 덮어씁니다. 출처는 historyProvenance에 남고, 제출된 주문은 초안으로 돌아가 다시 확인·제출이 필요합니다. 날짜·시간·받는 분·호실·금액·결제는 복사되지 않습니다.

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>",
      "requestId": "<requestId>",
      "revision": "<revision>",
      "sourceOrderId": "<sourceOrderId>",
      "profileId": "<profileId>",
      "ownerCapability": "<ownerCapability>"
    },
    "name": "handam_public_apply_history"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say readOnly=false, idempotent=true, destructive=false; the description adds genuinely new behavior — sources are recorded in historyProvenance, and a submitted order reverts to draft and must be re-confirmed and re-submitted. That state-transition consequence is the most valuable disclosure here. It does not cover authorization needs or failure modes, so it is not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, front-loaded with the precondition, then fill rules, then side effects, then exclusions. No filler or restatement of the tool name, and each sentence carries actionable information.

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?

For a 9-parameter mutation tool with no output schema, the description covers the important behavioral surface: preconditions, merge precedence, provenance, and the return-to-draft consequence. The gap is the undocumented identifier and fingerprint parameters and the absence of any note on authorization (ownerCapability), which the schema carries alone.

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 only 44%, and the description compensates only partially: it clarifies the meaning of overwrite (only paths the customer explicitly accepted) and the overall field-fill model. orderId, revision, requestId, sourceOrderId, and sourceFingerprint remain undocumented in both places, so the agent must infer their semantics.

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: applying a selected previous order to the current order, with fill-only-empty semantics. It implicitly separates itself from the preview step by requiring that the customer has already confirmed a preview, though it never names the preview sibling explicitly.

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

Usage Guidelines5/5

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

It gives an explicit precondition (call only after the customer confirms the preview) and explicit scoping rules: only empty fields are filled, and only paths listed in overwrite are replaced. It also lists what will never be copied (date/time, recipient, room, amount, payment), which is exactly the boundary information an agent needs before invoking.

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