Skip to main content
Glama

복대리 · Bokdaeri

복대리 AI 상담 신청·관리 권한 설정

begin_consultation_permission

Return the consent page for granting or renewing AI consultation permission.

본인 상담의 AI 신청·수락 전 수정·철회 위임을 설정하거나 갱신할 복대리 웹 동의 주소와 현재 권한 상태를 반환합니다. 위임은 이용자가 웹에서 동의해야 부여됩니다.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations declare readOnlyHint=false and idempotentHint=false, which implies a state change, yet the description only says it returns a URL and current status. The most valuable disclosure is that the delegation is not granted by the call itself; it requires the user's web consent. However, why the call is non-read-only and non-idempotent is not explained.

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 English lead sentence gives the core action, and the Korean sentence adds the scope and precondition, so the structure is front-loaded with no filler. The second sentence is dense but every clause, such as '웹 동의 주소' and '현재 권한 상태', adds 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?

The tool is param-free and has no output schema, and the description covers both the returned URL and the current permission status and adds the key constraint that the user must consent on the web. It lacks only follow-up guidance, such as what to do after consent or how to verify that the delegation took effect.

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?

There are zero parameters, so the baseline is 4, and the description adds no parameter claims that would need to compensate. It notes the returned consent URL and current permission state, which is a useful hint about the shape of the result.

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 uses a specific verb and object pair ('Return the consent page') and names the exact permission being handled: AI consultation request/management delegation. The Korean sentence 'AI 신청·수락 전 수정·철회 위임' ties it to a concrete resource and scope, which separates it from the contact-related siblings. It is clear but does not name a sibling 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?

The description states the setting (grant or renew the delegation), so the intended context is implied, but it never says when not to call it or which sibling handles revocation (revoke_consultation_permission) or status checks. The only clear rule is that consent must happen on the web.

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