Skip to main content
Glama

복대리 · Bokdaeri

복대리 연락처 변경 시작

begin_contact_change

Return a verification link to change the default contact or the contact for one pending consultation.

향후 상담의 기본 연락처 또는 지정한 수락 대기 상담 한 건의 연락처를 변경할 때 사용합니다. 웹 인증 주소와 확인 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": {
      "purpose": "<purpose>"
    },
    "name": "begin_contact_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNo이용자가 이번 대화에서 직접 말한 새 번호(선택). 화면에 미리 채우기만 합니다.
purposeYes
request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint false, destructiveHint false, idempotentHint false), the description discloses the key non-obvious behavior: it returns a web verification URL and confirmation ID, and the new number is not applied until the user verifies and applies it on the web. That materially changes how an agent should report the outcome. It does not say whether unapplied links expire, how long the confirmation ID remains valid, or what happens if the flow is abandoned.

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 sentences, front-loaded with what the tool returns and followed by when to use it; nothing is padded. The English and Korean sentences are near-duplicates, which costs a little space but aids bilingual clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter flow-initiation tool with no output schema, the description covers the return payload (URL plus confirmation ID) and the deferred-application rule, which is the main thing an agent needs. It stops short of explaining how purpose and request_id interact or what state the consultation is left in after the link is issued.

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 only 33% – only the phone parameter is documented. The description partially compensates by implying that the one-pending-consultation case involves a specific target (the request_id), but it never explains the purpose enum values (default vs request) or when request_id is required versus forbidden. This leaves the most decision-relevant parameter meaning undocumented.

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 concrete verb and result (return a verification link) and scopes the resource precisely to two cases: the default contact for future consultations, or the contact of one pending accepted consultation. It is clear what the tool does without opening the schema, though it doesn't name which sibling handles the adjacent verification or status steps.

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?

"사용 시점" gives an explicit condition for calling: when changing the default contact or the contact of one pending consultation. However, there is no when-not guidance and no routing to alternatives such as begin_contact_verification or get_contact_change_status, so the agent must infer the boundaries of this flow itself.

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