Skip to main content
Glama

도플리 FAQ 검색 / Search Doply FAQ

search_faq
Read-onlyIdempotent

도플리(Google Play 비공개 테스트 대행) 자주 묻는 질문을 검색합니다. 요금, 기간, 환불, 지원 앱 유형, SDK 조건, 업데이트, 프로덕션 승인 등. query 를 비우면 질문 목록 전체를 돌려줍니다. / Search the Doply (Google Play closed testing service) FAQ: pricing, test period, refunds, supported app types, SDK requirements, updates, production access. Leave query empty to list all questions.

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": "search_faq"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
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

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description adds the browse-all behavior for an empty query, but says nothing about result volume, ranking, truncation, or what a hit contains. Useful but thin beyond the structured data.

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 scoping and empty-query behavior are front-loaded, which is good, but the entire content is stated twice in Korean and English with no added information in either pass. The bilingual mirror roughly doubles length without earning the extra sentences.

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?

There is no output schema, so the description carries the burden of explaining what comes back; it only says an empty query "returns all questions" and never characterizes the result shape (question/answer text, IDs, language of returned content). For a two-parameter read tool this is adequate but leaves a real gap.

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 description coverage is 50%: `language` is documented in the schema, while `query` carries only a maxLength constraint. The description partly compensates by defining empty-query behavior, but never states the matching semantics (keyword, substring, or natural-language) or the 200-character limit. This sits at the baseline for a half-documented two-parameter schema.

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 ("Search the Doply FAQ") and enumerates the covered topic areas — pricing, test period, refunds, supported app types, SDK requirements, updates, production access. That scope is concrete enough to separate it from get_contact and get_service_info, though the overlap with get_requirements ("SDK requirements") is not addressed.

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?

"Leave query empty to list all questions" is a genuine usage instruction that tells the agent how to browse rather than search. However, there is no guidance on when to prefer this over the siblings get_requirements or get_service_info, and no statement of when this tool is the wrong choice.

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