Skip to main content
Glama

내 프로필 초기화(연결 해제)

handam_public_reset_profile
Destructive

본인 프로필을 해제합니다: 저장된 기본값이 삭제되고 ownerCapability가 즉시 무효화됩니다. 이미 접수된 주문은 운영자 처리를 위해 남습니다.

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>"
    },
    "name": "handam_public_reset_profile"
  }
}

Input Schema

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

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?

Although annotations already flag destructiveHint=true and idempotentHint=false, the description supplies the specific consequences an agent needs: saved defaults are deleted, ownerCapability is invalidated immediately, and already-submitted orders survive for operator handling. That last clause is exactly the boundary information annotations cannot convey.

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 tight sentences with zero filler: the action and its destructive effects come first, and the scope caveat about existing orders follows. Every clause carries decision-relevant information.

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 destructive, non-idempotent operation with no output schema, the description covers the main risks (deleted defaults, invalidated capability) and the persistence boundary for live orders. It does not state recovery options or what an agent should do after invalidation (e.g., whether re-registration is required), leaving a modest gap.

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 100%, so both profileId and ownerCapability are already fully documented, including the key insight that profileId is only a lookup key. The description adds one useful semantic — that ownerCapability becomes void after this call — but no format, length, or validation detail beyond the schema.

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 action ('본인 프로필을 해제합니다') and resource ('본인 프로필'), and the added detail that saved defaults are deleted makes it clearly distinct from save-profile-style siblings. It stops short of explicitly naming a sibling operation, so it reads as clear-but-undifferentiated rather than fully routing.

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?

Usage is only implied: an agent can infer this is the teardown counterpart to saving profile defaults, and the note about already-submitted orders hints at it being safe to run after ordering. There is no explicit when/when-not guidance, no statement of prerequisites (e.g., needing a valid ownerCapability from first registration), and no named alternative.

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