Skip to main content
Glama

복대리 · Bokdaeri

복대리 상담 수정·철회 준비

prepare_consultation_change

Prepare a preview of an edit or withdrawal for a pending consultation without applying it.

변호사 수락 전인 본인 상담의 수정안 또는 철회안을 준비합니다. 수정에는 변경 후 전체 요약·유형·단계가 필요합니다. 철회에는 대상 상담과 현재 버전만 지정하면 됩니다. 확인할 내용과 확인 방법을 반환하며, 적용은 별도 단계입니다.

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": {
      "request_id": "<request_id>",
      "revision": "<revision>",
      "change": "<change>"
    },
    "name": "prepare_consultation_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNo
changeYes
summaryNo
categoryNo
revisionYes
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is carried by structured data. The description adds genuinely non-structured context: no change is applied, a preparation artifact is produced, and the tool returns items to confirm plus how to confirm them. The mild tension between 'preview, not applied' and readOnlyHint=false is reconciled by the explicit statement that preparation and application are separate steps, so it is not a contradiction.

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 front-loads the core action and the no-apply constraint before the operational detail. The subsequent Korean text is largely additive rather than repetitive, though the bilingual duplication of the same framing costs some density.

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 preparation tool with six parameters, no output schema and no schema descriptions, the definition covers preconditions, per-change-type input requirements, what is returned, and what happens next. What remains unstated (idempotency of repeated preparation, what happens to a stale revision) is minor for this tool's role.

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?

Schema description coverage is 0%, so the description must compensate, and it does: it explains that an edit requires the full post-change summary, category and stage, while a withdrawal only needs the target consultation and the current version (revision). That maps required inputs to each value of the change enum, which the bare schema does not. The meaning of individual enum members is still left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: preparing a preview of an edit or withdrawal for a pending consultation, explicitly without applying it. It also scopes the target to the caller's own consultation before lawyer acceptance, which separates it from apply_consultation_change and discard_consultation_change without needing their schemas.

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?

It gives a clear precondition (only before lawyer acceptance, only for one's own consultation) and states that applying is a separate step, which implicitly routes the agent elsewhere for the actual change. It stops short of naming the apply/discard sibling tools explicitly, so the routing is strong but not fully spelled out.

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