Skip to main content
Glama

제출 전 확인 요약 (버전 지문 포함)

handam_public_preview_confirmation
Read-onlyIdempotent

고객에게 그대로 보여 줄 현재 초안 전체와 남은 항목·상담 항목, 그리고 이 정확한 버전을 가리키는 confirmationFingerprint를 반환합니다(읽기 전용). 고객의 "네"라는 말만으로는 제출되지 않으며 이 지문과 revision으로 handam_public_submit_for_review를 호출해야 합니다. 가격·재고·배송 약속은 없습니다.

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>",
      "profileId": "<profileId>",
      "ownerCapability": "<ownerCapability>"
    },
    "name": "handam_public_preview_confirmation"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes
profileIdYes첫 접수 응답의 profile.profileId (조회 키일 뿐 권한이 아님)
ownerCapabilityYes첫 접수 응답에 한 번만 제공된 소유자 확인값. 클라이언트가 안전하게 보관해야 하며 다른 사용자와 공유하면 안 됩니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent with them ('읽기 전용'). Beyond that it adds real behavioral context: what the payload contains, that the fingerprint is version-specific, and that this call does not itself submit anything. It does not cover fallback behavior when the draft version is stale or the fingerprint is rejected, which keeps it from a 5.

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?

A single tight block that leads with what is returned, then the submission precondition, then the negative scope constraint about price, stock and delivery. Every sentence carries information; the closing constraint is terse enough to read as cryptic, but it is not padding.

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?

There is no output schema, so the description usefully enumerates the return contents and the fingerprint's role, which is the main thing an agent needs. For a three-required-parameter tool with a capability token, it leaves open what happens on a stale or mismatched fingerprint and whether the caller should act if remaining items are non-empty.

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% — profileId and ownerCapability are already documented in the schema, including the important warning that ownerCapability is a secret and profileId is only a lookup key. The description adds no parameter-level meaning at all, not even for orderId, which is undocumented in the schema, so it does not compensate for the remaining gap.

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?

States a specific verb (returns) and a precisely enumerated payload: the full current draft as shown to the customer, remaining/consultation items, and a confirmationFingerprint pinning this exact version. It is clearly distinguishable from the submission tool it names, so an agent can tell the two apart without opening schemas.

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?

Explicitly states that a customer's verbal 'yes' is not sufficient and that handam_public_submit_for_review must be called with this fingerprint and revision, which gives the agent a clear condition for choosing this tool as the pre-submit step. The only gap is that it never says the inverse case (e.g. when there is nothing left to confirm, or when to skip this preview).

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