Skip to main content
Glama

복대리 · Bokdaeri

복대리 상담 목록

list_consultation_requests
Read-onlyIdempotent

List only consultation requests belonging to the authenticated connection.

이 연결에서 열람할 수 있는 본인의 접수 상담을 최근순으로 한 번에 최대 5건 반환합니다. 각 항목에는 상담 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": "list_consultation_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered; the description adds real value beyond that by disclosing the hard cap of 5 items per call, recency ordering, and the per-item fields (ID, status, edit/withdraw eligibility, viewable summary). It does not explain what happens on pagination fatigue or whether results are eventually consistent.

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 scope statement is front-loaded in one English sentence, then the return behavior is elaborated compactly. The bilingual duplication adds some redundancy but no filler or hedging.

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?

With no output schema, the description usefully enumerates the returned item fields and the per-call cap. However, for a cursor-paginated list tool with a 0%-covered schema, the omission of cursor semantics leaves an agent unable to correctly walk past the first 5 results.

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?

Schema description coverage is 0%, so the description must carry the two parameters itself. It conveys the maximum of 5 ('한 번에 최대 5건'), which maps to the limit bound, but says nothing about the cursor parameter — its format, opacity, or how to obtain the next one — leaving half the parameters undocumented.

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 gives a specific verb and resource ('List ... consultation requests') plus an explicit scope restriction ('only ... belonging to the authenticated connection', '본인의 접수 상담'). It is clearly distinguishable from mutation-oriented siblings like apply_consultation_change or submit_consultation_request, though no sibling is named directly.

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 the scope statement — this is the way to view your own received consultations — but there is no explicit when-to-use/when-not framing and no pointer to alternative tools for other views (e.g., status lookups via get_consultation_status).

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