Skip to main content
Glama

복대리 · Bokdaeri

복대리 상담 변경 결과 확인

get_consultation_change_status
Read-onlyIdempotent

Read the actual result of the specified change review.

미리보기 ID(review_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": {
      "review_id": "<review_id>"
    },
    "name": "get_consultation_change_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
review_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the narrow clarification that the validity period is not extended — genuinely beyond the annotations — but does not describe the shape of the result or whether a pending change returns a different status than an applied one.

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 lead sentence states the action immediately, followed by the Korean elaboration and the negative constraints; nothing is buried. The bilingual restatement is slightly redundant but short enough that it costs little.

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-only status check with no output schema, the description covers what is returned at a high level (current status and application result) and what side effects do not occur. Remaining gaps — status value vocabulary and behavior for invalid or expired IDs — are moderate but not blocking for invocation.

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 schema alone gives only a 32-hex string pattern. The description compensates by identifying review_id as the '미리보기 ID' — the preview identifier from a prior preparation step — which tells an agent where the value must come from. It does not explain what happens if the ID is stale or unknown.

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 actual result of the specified change review') and elaborates what is retrieved ('현재 상태와 적용 결과'). It carves itself out from the mutation siblings by stating it does not create or apply a change plan, though it does not explicitly distinguish itself from read-side siblings like get_consultation_status or get_consultation_change_options.

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 clear context for use: call it with a preview ID to check the status and application result of an existing change proposal. It also states what the tool is not for (creating, applying, or extending validity), which is a useful exclusion. It stops short of naming an alternative tool for those other actions.

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