Skip to main content
Glama

도플리 문의처 / Contact Doply

get_contact
Read-onlyIdempotent

사람에게 직접 문의해야 할 때의 연락처 (이메일, 카카오 채널, 크몽 구매자는 크몽 채팅). / How to reach a person at Doply (email, Kakao channel, Kmong chat for Kmong buyers).

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

Input Schema

NameRequiredDescriptionDefault
languageNo응답 언어. 고객이 질문한 언어로 지정하세요 / response language: set it to the language the customer is asking inko

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / language / description
      Previous value: -"응답 언어 / response language"New value: +"응답 언어. 고객이 질문한 언어로 지정하세요 / response language: set it to the language the customer is asking in"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the safety profile is covered. The description adds genuinely new context absent from annotations: the channel differs by customer type (Kmong buyers must use Kmong chat), which changes what the agent tells the user.

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

Conciseness5/5

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

A single front-loaded sentence per language with the channel list parenthesized at the end. No filler, and the bilingual pairing is functional for a Korean/English service.

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 no-args, non-destructive lookup with full annotation coverage, the description is sufficient to call it correctly. The only minor gap is that it does not hint at what the response contains, but no output schema exists and the channel list implicitly signals the payload.

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 coverage is 100% and the single 'language' parameter already carries its own description and enum, so the description adds nothing about it. Baseline 3 applies when the schema does the heavy lifting.

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?

States a concrete resource (contact channels: email, Kakao channel, Kmong chat) and the situation it serves ('reaching a person at Doply'). The phrase '사람에게 직접 문의해야 할 때' implicitly separates it from search_faq and get_service_info, though no sibling is named explicitly.

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?

Gives a clear triggering condition: use it when the user needs to contact a human directly. It does not state when NOT to use it (e.g., that FAQ questions should go to search_faq first), so the routing is left partly to inference.

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