Skip to main content
Glama

도플리 서비스 정보 / Doply service info

get_service_info
Read-onlyIdempotent

도플리 서비스 개요: 테스터 수, 테스트 기간, 기기, 일일 실행 스케줄, 스크린샷, 크래시 리포트, 요금, 공식 판매처, 조직 계정 해당 여부, MCP 키 받는 곳. / Doply overview: number of testers, test period, devices, daily launch schedule, screenshots, crash reports, pricing, official sales channels, organization accounts, where to get an MCP key.

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

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's contribution is the scope of facts available, but it says nothing about whether the data is static or versioned, how current it is, or how the response is shaped.

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 topic is front-loaded, but the same ten-item inventory is repeated verbatim in Korean and English, roughly doubling length without adding information. The list is useful for keyword matching, yet it reads as a content dump rather than a directed statement of purpose.

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 simple, read-only, zero-required-parameter lookup with a fully documented schema and no output schema, the description covers the domain of returned facts adequately. The remaining gap is routing guidance against the three sibling tools, which matters because several of them could plausibly answer an overlapping question.

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?

The single optional 'language' parameter has full schema coverage including an enum and an explicit instruction to match the customer's language. The description adds nothing about the parameter, so baseline 3 applies; the schema is doing all the work here.

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 enumerates the concrete facts the tool returns (tester count, test period, devices, launch schedule, screenshots, crash reports, pricing, sales channels, org account eligibility, MCP key location), so an agent can recognize it as a static service-overview lookup. It lacks an explicit verb like 'retrieve' and never names the sibling tools, but the content inventory is specific enough to separate it from get_contact, get_requirements and search_faq.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no exclusions, and no routing to alternatives. An agent must infer from the item list that this is the right call for general 'what is Doply / how much does it cost / where do I get an MCP key' questions rather than for contact or requirement 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