Skip to main content
Glama

한담 Agent와 주문 보완 대화

handam_public_converse
Idempotent

접수 응답의 sessionId로 한담 서버 Gemini Agent에게 부족한 주문정보를 보완합니다. profileId와 ownerCapability를 매번 검증합니다. 명시된 정보로 비어 있는 초안 항목만 채우며 기존 값과 충돌하면 그대로 유지하고 알립니다. 확정·발주·결제·고객발송은 하지 않습니다. 최신 revision을 사용하고 재시도에는 같은 requestId와 내용을 보냅니다. 확인값은 text에 쓰지 말고 전용 인자에만 넣으세요.

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>",
      "sessionId": "<sessionId>",
      "requestId": "<requestId>",
      "revision": "<revision>",
      "text": "<text>",
      "profileId": "<profileId>",
      "ownerCapability": "<ownerCapability>"
    },
    "name": "handam_public_converse"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations it discloses the real behavioral contract: profileId and ownerCapability are re-verified on every call, existing values are preserved with a notification on conflict, the latest revision is used, and retries must reuse the identical requestId and payload. This is fully consistent with idempotentHint=true and destructiveHint=false, and the explicit exclusion of confirm/order/pay/customer-send resolves any ambiguity left by readOnlyHint=false.

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 purpose is front-loaded in the first sentence and each subsequent sentence adds a distinct constraint (validation, fill-only rule, no side effects, retry identity, text safety). Dense but no sentence is filler; the only friction is the reference to 'dedicated arguments' that the schema does not define.

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 7-required-parameter mutation tool with no output schema, the description covers the safety profile, idempotency, mutation scope, and the conflict-notification behavior that would otherwise be invisible. It stops short of describing what a successful response contains (updated draft, new revision, conflict notices), which matters without an output schema.

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?

With only 29% schema description coverage the description has to carry the load, and it does for most parameters: sessionId's origin, profileId/ownerCapability verification per call, requestId's idempotent-retry semantics, and the latest-revision rule. It also warns that confirmation values must not go into text and belong in dedicated arguments, though no such argument appears in the schema and orderId is never explained.

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 names a specific verb (보완 = fill in missing draft fields) and a specific resource (order draft via the Handam Gemini Agent conversation), anchored to the sessionId from the intake response. It also implicitly separates itself from submit/correct siblings by stating it only fills empty fields and never confirms, orders, pays, or messages customers, though it never names an alternative tool.

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?

It gives clear entry conditions (requires the sessionId issued in the intake response) and a precise scope rule: only explicitly stated information may fill empty draft fields, existing values win on conflict. Retry guidance (same requestId and same content) and the prohibition on confirm/order/pay/send are stated, but no sibling tool is named as the alternative for those actions.

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