Skip to main content
Glama

복대리 · Bokdaeri

복대리 AI 상담 신청·관리 권한 해제

revoke_consultation_permission
DestructiveIdempotent

Revoke AI consultation permission without withdrawing existing consultations.

이 연결에 부여한 AI 상담 신청·관리 위임을 현재 권한 버전으로 해제합니다. 이후 대리 신청·수정·철회가 제한되며 이미 접수된 상담은 유지됩니다.

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": {
      "expected_version": "<expected_version>"
    },
    "name": "revoke_consultation_permission"
  }
}

Input Schema

NameRequiredDescriptionDefault
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the description is not the sole source of the safety profile. It nevertheless adds real value beyond them by scoping the damage: only the delegation on 'this connection' is removed and already-submitted consultations survive, while subsequent proxy apply/modify/revoke is blocked. It does not cover behavior on a version mismatch or any auth requirements, keeping it out of 5 territory.

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 short sentences with the English summary front-loaded and the Korean detail following, and every clause carries information about scope or consequence. The cost is that the same content is effectively stated twice bilingually, which is mild redundancy rather than noise.

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?

For a single-parameter mutation with no output schema, the description covers the essential semantics: what is revoked, on which connection, and what is preserved. The remaining gap is the version-mismatch/error path and the shape of the response, which an agent would want before calling a destructive tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter with 0% schema description coverage, so the description must carry the burden. The phrase '현재 권한 버전으로' hints that expected_version relates to optimistic concurrency, but it never states that the value must match the current version or what happens when it does not, leaving the agent to guess the parameter's contract.

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 gives a specific verb and resource ('Revoke AI consultation permission') and immediately bounds the scope with 'without withdrawing existing consultations' / '이미 접수된 상담은 유지됩니다'. This implicitly separates it from the cancel/discard siblings, but no sibling is named explicitly, so it stops short of a 5.

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 by the stated consequence ('이후 대리 신청·수정·철회가 제한되며'), which tells the agent what state change to expect. However, there is no explicit 'use this when…' clause, no prerequisites (e.g., that a permission must currently be granted), and no routing to alternatives such as begin_consultation_permission for the inverse operation.

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