Skip to main content
Glama

복대리 · Bokdaeri

복대리 상담 접수(위임)

submit_consultation_request
DestructiveIdempotent

Submit the confirmed preview only with current delegation and the server submission action.

최종 요약·비용·제공 범위를 이용자가 확인했고 서버가 접수 가능하다고 안내한 본인 상담을 접수합니다. 현재 미리보기, 상담·진행 버전과 유효한 위임을 검증합니다. 성공하면 참여 변호사에게 상담이 공개되고 알림 처리가 시작되며, 접수 영수증을 반환합니다.

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>",
      "delegation_version": "<delegation_version>",
      "journey_id": "<journey_id>",
      "expected_journey_revision": "<expected_journey_revision>",
      "review_id": "<review_id>"
    },
    "name": "submit_consultation_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYes
review_idYes
journey_idYes
request_idYes
delegation_versionYes
expected_journey_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, openWorld=true, and readOnly=false, so safety framing is covered. The description still adds real value beyond them: it discloses that validation of preview/revision/delegation occurs, that the consultation becomes visible to participating lawyers, that notification processing starts, and that a submission receipt is returned. It stops short of describing failure modes when validation fails.

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 short and front-loaded, leading with the commit condition and then the effects. The English lead sentence partially duplicates the Korean body and the mixed-language phrasing adds slight friction, but nothing is padding.

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 destructive, open-world commit operation with six required concurrency/version tokens and no output schema, the description covers preconditions and side effects but leaves the critical invocation inputs undocumented. A reader knows when to submit but not confidently how to fill the parameters, which is a meaningful gap for a terminal mutation.

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?

All six parameters are required with 0% schema description coverage, and the description never explains any of them by name or semantics. The phrase about validating 'current preview, consultation/progress version, and valid delegation' gestures vaguely at review_id, revision, journey_id, and delegation_version, but an agent still cannot tell these opaque version tokens apart or know how to obtain them.

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 states a specific verb and resource: it submits (접수) a finalized consultation request that has already been previewed and confirmed. It scopes the action as the terminal 'server submission action' following preparation, which separates it in spirit from prepare/continue/apply siblings, though no sibling is named explicitly.

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 gate: only submit when the user has confirmed the final summary, cost, and scope, and the server indicated the request is submittable with a current preview and valid delegation. It does not name alternatives (e.g., prepare_consultation_request, continue_consultation_request) for the case where those preconditions fail, so the routing guidance is implied rather than explicit.

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