Skip to main content
Glama

복대리 · Bokdaeri

복대리 연락받을 번호 확인

begin_contact_verification

Return a contact verification link, or the ready state if the connection is already verified.

이용자가 번호 확인이나 재인증을 요청했을 때 복대리 웹 인증 주소를 반환합니다. 이미 인증된 연결이면 새 주소 발급 없이 확인 완료 상태(phase=ready)를 반환합니다. 상담 준비·접수·알림은 발생하지 않습니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "begin_contact_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real behavioral detail beyond the annotations: an already-verified connection returns phase=ready without issuing a new address. The annotations declare readOnlyHint=false, making it consistent that a fresh verification link may be minted, and idempotentHint=false, consistent with a non-repeatable token issue. It also explicitly scopes out side effects (no consultation prep, intake, or alerts), which the annotations cannot express.

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?

Front-loads the outcome (link or ready state) and follows with the trigger condition and the side-effect exclusion. The English lead and Korean body restate the same content, which is slightly redundant but each part adds a distinct fact. Well sized for a parameterless tool.

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?

No output schema exists, and the description compensates by describing both possible returns (a verification link, or phase=ready). It also states what does not happen as a side effect. For a zero-parameter tool with annotations covering the safety profile, this is nearly complete, though the link's lifetime or reuse behavior is unstated.

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?

The tool takes zero parameters, so the schema carries no semantic burden and the description needs no parameter documentation. Baseline of 4 applies. The description usefully explains that the result is conditional on existing verification state, which is the closest thing to an input distinction here.

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?

States a specific verb and resource: return a contact verification link, or the ready state when the connection is already verified. The tool's scope is unmistakable. It doesn't explicitly contrast itself with siblings like begin_contact_change, but the purpose is clear without opening the schema.

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?

Names the triggering condition clearly: when a user requests number verification or re-verification (번호 확인이나 재인증). It also rules out adjacent behavior by noting no consultation preparation, intake, or notification occurs. It stops short of naming an alternative tool for the adjacent flows, so it is not a full 5.

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