Skip to main content
Glama

내 프로필 기본값 조회

handam_public_get_profile
Read-onlyIdempotent

본인 프로필에 저장된 주문자 기본값(이름, 마스킹된 연락처, 상품·리본 선호)을 조회합니다. 받는 분·주소·날짜는 저장되지 않습니다.

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_get_profile"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds meaningful extra context: the contact value is masked on return and recipient/address/date are never persisted. It does not discuss the ownership-capability requirement or any rate/error behavior, so beyond-annotation value is moderate.

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?

Two tight sentences with the resource and returned fields front-loaded, then the negative scope second. No filler; slightly truncated on when-to-use rather than verbose.

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?

With no output schema, the description compensates by enumerating the returned fields and clarifying that contact data is masked — enough for an agent to know what a call yields. Safety is covered by annotations and parameters by the schema, so the remaining gap (prerequisites for the owner capability) is minor and already documented in the schema.

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%, and the schema itself documents both profileId ('조회 키일 뿐 권한이 아님') and ownerCapability (one-time owner confirmation, must not be shared) in more detail than any description could reasonably carry. The description adds nothing about parameters, which is acceptable given the schema baseline of 3.

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 the specific verb (조회) and resource (본인 프로필에 저장된 주문자 기본값) and enumerates the returned fields (이름, 마스킹된 연락처, 상품·리본 선호). It does not explicitly contrast with the sibling that writes these values (handam_public_save_profile_defaults), so the distinction is inferred rather than stated.

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: '본인 프로필에 저장된' signals a stored-defaults read, and the second sentence carves out what the profile does not hold (받는 분·주소·날짜). There is no explicit when-to-use statement or named alternative for retrieving order data instead.

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