Skip to main content
Glama

복대리 · Bokdaeri

복대리 연락처 변경 결과 확인

get_contact_change_status
Read-onlyIdempotent

Read whether the specified contact change was actually applied.

확인 ID(verification_id)로 지정한 연락처 변경의 진행 상태와 적용 결과를 조회합니다. 새 전화번호나 문자 인증번호는 반환하지 않습니다.

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": {
      "verification_id": "<verification_id>"
    },
    "name": "get_contact_change_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
verification_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral scope beyond those: it explicitly says the tool does not return the new phone number or the SMS verification code, which prevents an agent from expecting to retrieve credentials here. It stops short of describing the status value space or how in-progress results are represented.

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 definition is short and front-loaded, leading with the core read action and then the non-return caveat. The English and Korean lines are largely duplicative of each other, which is minor waste but not obscuring.

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 correctly takes responsibility for return content by naming the progress status and application result, plus the explicit exclusion of phone number and verification code. For a one-parameter read tool with full annotation coverage, the remaining gap (status enumeration, error behavior) is modest.

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 0% for the single parameter, so the description must carry the load, and it does only partly. It identifies verification_id as the '확인 ID' that designates a specific contact change, which is more than the bare regex pattern in the schema, but it omits where the ID comes from and what happens on an unknown or expired ID.

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 states a specific verb and resource: 'Read whether the specified contact change was actually applied', which is complemented by the Korean line naming the retrieved fields (진행 상태, 적용 결과). It clearly distinguishes a contact-change status read from consultation-oriented siblings by naming contacts, though it never names an alternative tool explicitly.

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 implied rather than stated: the tool reports whether a change 'was actually applied', which suggests polling after a begin/apply step, but there is no explicit when-to-use or when-not guidance. Nothing routes the agent away from get_consultation_change_status or tells it whether to call this before or after begin_contact_change.

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