Skip to main content
Glama

도플리 이용 조건 / Doply requirements

get_requirements
Read-onlyIdempotent

도플리로 비공개 테스트를 진행하기 위한 필수·권장 조건 (비공개 트랙, 출시 국가 한국, minSdk, 유료 앱, TWA 미지원). / Required and recommended conditions for a closed test with Doply (closed track, South Korea as a release country, minSdk, paid apps, no TWA).

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

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered by structured data. The description adds the content scope of the fixed requirement set, which is genuinely useful context, but says nothing about result shape or whether the conditions are versioned or subject to change. Adequate, not rich.

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 definition is one front-loaded sentence per language, with the resource named first and the covered topics parenthesized. The bilingual duplication doubles the character count, but that is defensible given the language parameter and Korean-speaking audience, so it is not wasted wording.

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?

This is a simple, zero-required-parameter lookup with annotations covering its behavior and no output schema to explain. The description lists the exact topics the answer covers, which is enough for an agent to decide to call it and to set expectations, though a hint about the return format (list of conditions vs. prose) is missing.

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?

There is a single optional parameter whose enum and instruction are fully documented in the schema (100% coverage), so the schema already does the work. The description adds nothing about the language parameter or its default, which is the correct baseline-3 outcome when schema coverage is complete.

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 resource (required/recommended conditions for a closed test with Doply) and enumerates the concrete topics it covers: closed track, South Korea release, minSdk, paid apps, no TWA. An agent can tell this is a static reference lookup rather than a contact or FAQ search. It does not explicitly name a sibling tool to distinguish itself, which keeps it at 4.

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 only implied: an agent can infer the tool is right when someone asks about prerequisites for a Doply closed test. There is no explicit 'use this when…' or 'do not use for…' guidance, and no pointer to search_faq or get_service_info for adjacent questions.

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