Skip to main content
Glama

복대리 · Bokdaeri

복대리 상담 요청 준비

prepare_consultation_request

Prepare or revise a consultation preview from the user facts without submitting it.

이용자가 변호사 상담 신청을 요청했을 때, 제공한 사실을 바탕으로 사건 유형·진행 단계와 10~200자 요약을 담은 미리보기를 준비합니다. 기존 초안은 진행 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": {
      "category": "<category>",
      "summary": "<summary>",
      "stage": "<stage>"
    },
    "name": "prepare_consultation_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageYes
resumeNo
summaryYes사용자가 실제로 말한 상담 주제·문제·질문을 요약합니다. 신청하고 싶다는 문장만 넣지 않습니다. 내용이 없으면 도구를 호출하기 전에 사용자에게 묻습니다.
categoryYes
journey_idNo
expected_journey_revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare a non-read-only, non-destructive, closed-world, non-idempotent operation. The description adds useful boundary information that no authentication or submission occurs and that existing drafts can be revised, but it does not clarify whether the preview is persisted, how version conflicts are handled, or what happens on resume.

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 description is front-loaded and efficient, first stating the core action and then the no-submission boundary. There is some repetition between the English and Korean text and between 'without submitting it' and the later statement that submission has not started, but it is not verbose.

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 six-parameter mutation tool with no output schema and low schema description coverage, the definition covers the main purpose, the no-submission/no-auth boundary, and revision via journey ID/version. However, it does not explain the resume parameter, expected revision behavior, enum choices, or what the prepared preview returns.

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 only 17%, so the description must carry more weight. It maps the main fields by mentioning case type, stage, a 10–200 character summary, and revision via journey ID and version, but it leaves the resume boolean and expected revision conflict semantics underexplained, and it does not clarify enum meanings.

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 clearly states a specific verb and resource: prepare or revise a consultation preview from user facts without submitting it. It distinguishes from submission by stating submission and authentication do not begin at this stage, but it does not explicitly differentiate from nearby preparation/continue/change siblings.

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?

It gives a usage condition: when the user requests a lawyer consultation application. It also says existing drafts can be revised or resumed via journey ID and version, but it does not explicitly say when to use this instead of continue_consultation_request, prepare_consultation_change, or submit_consultation_request.

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