Skip to main content
Glama

복대리 · Bokdaeri

복대리 연결·진행 상태 확인

get_consultation_connection_status
Read-onlyIdempotent

Read the current connection or specified journey without starting verification or submission.

현재 연결의 인증·권한 상태를 조회합니다. 진행 ID(journey_id)를 지정하면 해당 상담 준비의 최신 단계와 가능한 다음 동작을 반환합니다. 조회로 새 인증이나 접수가 시작되거나 유효기간이 연장되지는 않습니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_consultation_connection_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
journey_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 still adds real value beyond that: it states that reading will not initiate authentication, will not create a submission, and will not extend any validity period, plus that it returns the latest stage and possible next actions.

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 behavior constraint is front-loaded and the text is short. The English lead sentence and the Korean body restate the same 'no verification/submission' guarantee, which is mild redundancy rather than bloat.

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?

With one optional parameter, rich annotations and no output schema, this covers what an agent needs: default vs journey-scoped behavior, side-effect guarantees, and the shape of the response (latest stage, possible next actions). A brief note on what the current-connection result looks like when no journey exists would close the remaining gap.

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 carry the param. It does explain that journey_id is optional, that omitting it targets the current connection, and that supplying it switches the result to that journey's latest step and next actions. Only the 32-character hex format is left to the schema pattern.

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 opening sentence names a specific verb and resource ('Read the current connection or specified journey status'), and the Korean text narrows it to authentication/permission state. The clause 'without starting verification or submission' implicitly separates it from the begin_*/submit_* siblings, though it never names them, and it is not clearly distinguished from get_consultation_status.

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: call it to inspect status, optionally scoping to a journey to get the latest step and permissible next actions. The negative clause rules out starting verification or submission, hinting that other tools do that, but no alternative is named and there is no explicit when-not guidance.

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