Skip to main content
Glama

꽃 주문 미확정 초안 접수 (로그인 없음)

handam_public_submit_flower_request
Idempotent

한담에 미확정 꽃 주문을 1건 접수합니다. 필수 항목이 모두 있으면 requested(접수 완료·운영자 검토 대기, 확정 아님·결제 대기), 미완성이면 draft 상태이며 배송·발주를 예약하지 않습니다. 사용자가 입력한 내용을 그대로 보여 주고 동의를 받은 뒤 호출하세요. requestId는 의도마다 새 UUID v4를 만들고 재시도에는 같은 requestId와 같은 내용을 보내면 같은 주문이 중복 없이 반환됩니다. 첫 응답의 profile.ownerCapability는 한 번만 제공되므로 안전하게 보관하세요. 이전 profile을 함께 보내면 비어 있는 주문자 연락처·상품·리본 기본값만 채워지고, 받는 분·주소·날짜는 절대 자동 재사용되지 않습니다. 전화번호는 한국 번호(010-1234-5678 또는 +82 10-1234-5678)만 받습니다. 테스트는 isTest=true.

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": {
      "requestId": "<requestId>",
      "draft": "<draft>"
    },
    "name": "handam_public_submit_flower_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYes고객이 저장·제출하는 미확정 주문 초안. 저장 시에는 모든 항목이 비어 있어도 되지만, 존재하는 값은 형식을 지켜야 합니다. 제출 조건은 x-handam.submitRequired / conditionalFields 참고. 가격·결제·확정 필드는 없습니다.
isTestNo테스트 접수 표시(저장 후 해제 불가).
profileNo같은 주문자의 이전 프로필(선택). 잘못되면 접수 자체가 거부됩니다.
requestIdYes이 접수 의도의 멱등 키(UUID v4). 재시도에는 같은 값을 재사용합니다.
provenanceNo클라이언트가 밝히는 출처 메모. 서버는 미검증(unverified)으로만 기록합니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, it explains that full required fields produce requested status while incomplete input stays draft, and that no delivery or ordering is reserved. It also discloses idempotent retry semantics, one-time ownerCapability handling, profile fill behavior with explicit exclusions, phone format, and test-only flagging.

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?

The description is front-loaded with purpose and status outcomes, then moves through consent, idempotency, profile handling, validation, and testing. It is dense but every sentence carries relevant operational meaning, with no obvious filler.

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 complex nested-draft submission tool with no output schema, it covers the key status behavior, consent requirement, idempotency, profile capability handling, default-fill exclusions, and validation. It does not fully describe the response shape beyond ownerCapability and status outcomes, but it provides enough behavioral context for correct invocation.

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 100%, so the baseline is 3, but the description adds practical meaning: requestId reuse requires the same content, previous profile data fills only blank contact/product/ribbon defaults and never recipient/address/date, and ownerCapability must be stored safely. It also gives example accepted phone formats and clarifies isTest=true.

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: receiving one unconfirmed flower order as a draft/requested intake. It clearly distinguishes unconfirmed reception from confirmation, payment, delivery, and ordering, but it does not explicitly compare itself with sibling tools such as handam_public_submit_for_review.

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?

It gives a useful workflow prerequisite: show the user's input verbatim and obtain consent before calling. However, it does not explicitly state when to use this tool versus correction, status lookup, or submit-for-review alternatives.

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