Skip to main content
Glama

복대리 · Bokdaeri

복대리 상담 수정·철회 적용(위임)

apply_consultation_change
DestructiveIdempotent

Apply the exact confirmed change only with current permission and the server action.

이용자가 확인한 수정안 또는 철회안을 유효한 관리 위임으로 변호사 수락 전에 적용합니다. 미리보기 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": {
      "review_id": "<review_id>",
      "expected_revision": "<expected_revision>"
    },
    "name": "apply_consultation_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
review_idYes
expected_revisionYes

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 openWorldHint=true, so retry-safety is partly given; the description still adds real context by naming the side effect (applied content may be disclosed to participating lawyers or trigger notification processing) and the optimistic-concurrency behaviour (preview ID and expected revision are validated). What is missing is failure behaviour on a revision mismatch and whether the mutation is reversible — material for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operative content is front-loaded and reasonably tight, but the English lead sentence and the Korean body cover the same ground without the English adding detail, so roughly half the text is duplication. The most decision-relevant fact for an agent (the destructive disclosure/notification side effect) is buried at the end.

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 two-parameter destructive mutation with no output schema, the description covers delegation, timing, idempotency and side effects, which is solid. It still leaves the agent without any statement of what a successful apply returns or what to do when expected_revision does not match, and the English summary is too loose to compensate for the language split.

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%, so the description must carry parameter meaning, and it only gestures at it: '미리보기 ID와 예상 버전을 검증' loosely maps to review_id and expected_revision but never explains that review_id is the 32-hex preview handle produced by the prepare step, nor that expected_revision is a concurrency guard whose mismatch fails the call. The regex constraint and the mismatch outcome are left entirely 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 Korean body states a specific verb and object: applying a user-confirmed revision or withdrawal proposal ('이용자가 확인한 수정안 또는 철회안... 적용'), scoped to the window before lawyer acceptance. This distinguishes it from prepare/discard siblings in substance, though no sibling is named explicitly and the English lead sentence is far vaguer than the Korean body.

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?

Prerequisites are implied rather than enumerated: 'the exact confirmed change only with current permission', a valid management delegation, and 'before the lawyer accepts' together tell the agent this must follow a confirmation step. However, it never states when NOT to use it or what the alternative is when the change is unconfirmed or the delegation is missing (e.g. discard or prepare), leaving the routing to inference.

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