Skip to main content
Glama

복대리 · Bokdaeri

복대리 상담 이용 안내

get_consultation_service_info
Read-onlyIdempotent

Explain Bokdaeri consultation fees, privacy and the request process without creating a draft.

복대리는 법률 상담을 원하는 이용자와 한국 변호사를 연결하는 서비스입니다. 상담 비용, 신청 절차와 개인정보 제공 범위를 안내합니다. 상담 초안이나 접수 건은 생성하지 않습니다.

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_service_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description reinforces that no draft or submission record is produced and enumerates the informational content returned (fees, privacy scope, process), which is useful scope detail beyond the annotation flags, though it says nothing about response shape or language of the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded English sentence with the 'no draft' exclusion is well structured and wastes nothing. However, the Korean block largely restates the same three topics (fees, process, privacy) and repeats the no-draft statement, so roughly half the text is duplicated content rather than added information.

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 zero-parameter, read-only informational tool with no output schema, the description is complete enough: it says what subject matter comes back and that nothing is persisted. It could add one clause on the format/language of the returned guide, but nothing needed to invoke it correctly is missing.

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?

The tool takes zero parameters and the schema is an empty object, so there is no parameter semantics to explain; the baseline for a parameterless tool applies. The description correctly implies no input is needed to retrieve the guide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Explain Bokdaeri consultation fees, privacy and the request process') and immediately sets scope against the sibling cluster by stating it does not create a draft or a submission. An agent can distinguish this static-information tool from prepare_consultation_request or submit_consultation_request without inspecting any schema.

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 implies the trigger clearly (user asking about fees, privacy scope, or application steps) and gives an explicit when-not ('without creating a draft', '상담 초안이나 접수 건은 생성하지 않습니다'). It stops short of naming a concrete alternative sibling to route to when the user actually wants to start a request.

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