Skip to main content
Glama

내 주문 항목 명시적 수정

handam_public_correct_request
Idempotent

고객이 명시적으로 밝힌 값으로 본인 초안 항목을 직접 바꿉니다(점 표기 경로 → 값). 서버 Agent가 채우지 않은 충돌 값을 반영할 때 사용하며, 제출된 접수도 초안으로 되돌립니다. isTest·reception은 바꿀 수 없습니다. 확정·결제·배송 예약이 아닙니다.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses two non-obvious behaviors: already-submitted receptions get reverted to draft, and isTest/reception are immutable. It does not explain how revision conflicts are reported, which matters for a mutating, idempotent tool.

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?

Four short, front-loaded sentences: action, when-to-use, constraints, then exclusions. Dense but every clause carries information; nothing is filler.

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

Completeness3/5

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

A 6-required-param mutation with nested objects, no output schema, and no annotation for conflicts; the description covers mutability and side effects well but leaves the revision/optimistic-concurrency model and failure behavior undocumented. An agent could call it but might mishandle version conflicts.

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?

The description explains the `changes` map syntax (dot path → value) and constrains its keys indirectly via the immutability note, adding meaning to a param the schema only types loosely. However, schema coverage is 33% and `revision` (clearly a concurrency token) plus `orderId`/`requestId` are never explained in either place, leaving a real gap.

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?

States a concrete verb and resource (changing the caller's own draft items to explicitly stated values) and explains the change format as dot-notation path to value. It also clarifies scope by noting submitted receptions are reverted to draft. It does not name a sibling, but the scope is specific enough to separate it from preview/confirm/submit tools.

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?

"서버 Agent가 채우지 않은 충돌 값을 반영할 때 사용" gives an explicit trigger condition, and "확정·결제·배송 예약이 아닙니다" gives an explicit exclusion. No sibling is named as an alternative, so it stops short of full routing guidance.

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