Skip to main content
Glama

복대리 · Bokdaeri

복대리 상담 상태 확인

get_consultation_status
Read-onlyIdempotent

Read the specified consultation receipt, current status and permitted lawyer information.

request_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": {
      "request_id": "<request_id>"
    },
    "name": "get_consultation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond them by disclosing conditional return content (lawyer public info only when accepted) and the semantic caveat that acceptance does not equal a completed call; it does not address authorization scope or failure behavior.

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 summary is front-loaded and followed by concrete Korean detail, with the important caveat placed last as a qualifier. There is mild duplication between the English and Korean sentences, but nothing is wasted.

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 read tool with rich annotations and no output schema, the description covers what is retrieved and the key state distinction. The remaining gap is operational: no guidance on obtaining request_id or on error/empty results.

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 schema gives no meaning for request_id beyond a 32-char hex pattern. The description partially compensates by stating it refers to the caller's own consultation, but it never explains where the ID comes from or what happens on an unknown ID.

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 names a specific verb and resource ('Read the specified consultation receipt, current status and permitted lawyer information') and enumerates what is returned: latest status, receipt details/time, cost, follow-up guidance, and lawyer public info for accepted cases. It does not differentiate itself from similarly named siblings such as get_consultation_change_status or get_consultation_connection_status, 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 'request_id로 본인 상담의...' (query the caller's own consultation), and the closing note clarifies that acceptance and actual call completion are separate states. However, there is no explicit when-to-use/when-not-to-use guidance and no routing to any sibling tool, so an agent must infer which of the many consultation-status tools to pick.

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