Skip to main content
Glama

내 프로필 기본값 저장

handam_public_save_profile_defaults
Idempotent

주문자 본인이 명시적으로 요청할 때만 주문자 연락처·상품·리본 선호를 프로필에 저장합니다(전체 교체). 받는 분·주소·날짜는 저장할 수 없습니다.

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": {
      "profileId": "<profileId>",
      "ownerCapability": "<ownerCapability>",
      "defaults": "<defaults>"
    },
    "name": "handam_public_save_profile_defaults"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, and idempotent=true, so the write-and-repeat-safely profile is known. The description adds real value beyond that by disclosing the "전체 교체" full-replacement semantic and by listing which data classes are out of scope, but it says nothing about failure modes for a wrong profileId/ownerCapability or what the response returns.

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?

Two sentences: the gating condition plus the action first, the exclusion second. No restatement of the title and no 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 3-parameter mutation tool with no output schema, the definition covers the trigger, the replacement semantics, and the data-class limits. Gaps remain around partial vs. complete defaults payloads and error behavior on an invalid capability, but nothing essential to a correct call is missing.

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 67%: profileId and ownerCapability are documented in-schema, while the nested defaults object has no field-level descriptions at all. The description compensates by enumerating the saveable preference groups (contact, product, ribbon) and flagging that the save is a full replacement rather than a merge, which the schema does not convey.

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 and resource (saves the orderer's contact/product/ribbon preferences into the profile) and bounds the scope by stating what cannot be stored (recipient, address, date). It does not explicitly contrast itself with siblings such as reset_profile or get_profile, so the distinction is left partly implicit.

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?

"주문자 본인이 명시적으로 요청할 때만" gives a clear, explicit trigger condition: only when the orderer themselves asks. It does not name an alternative tool or describe what to call instead when the condition is not met, so it stops short of full when/when-not/alternative 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