Skip to main content
Glama
coolapk-mcp-pro

coolapk-mcp-pro

by yufeng-liang

coolapk_app_detail

查看酷安应用详情(包名 → 应用名、简介、关注数、下载量、版本)。

Instructions

查看酷安应用详情(包名 → 应用名、简介、关注数、下载量、版本)。

搜到应用相关动态后,用包名查应用本身:判断「这是不是同一个 App」 「现在的最新版本号」比只看帖子标题可靠。

Args: package_name: 应用包名(如 com.coolapk.market)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "package_name": "<package_name>"
    },
    "name": "coolapk_app_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
package_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does establish that this is a read-only lookup and lists the returned fields, which is real value. It says nothing about behavior on an invalid/unknown package name, rate limits, or auth requirements, so gaps remain for a no-annotation tool.

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?

Front-loaded with the purpose and return fields, then the usage rationale, then the argument. The middle sentence earns its place by justifying the tool over title-based inference, though the parenthetical arrows and quoted phrases make it slightly denser than necessary.

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 one-parameter read tool with an output schema, the description covers purpose, when to reach for it, and the argument format, which is nearly everything an agent needs. Only error/edge-case behavior for an unknown package is unaddressed.

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?

Schema coverage is 0%, but the description compensates by explaining package_name as the app's 包名 and giving a concrete example format (com.coolapk.market), which the schema does not. That is enough to call the tool correctly for its single parameter.

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?

States a specific verb and resource (查看酷安应用详情) and enumerates exactly what comes back: 应用名、简介、关注数、下载量、版本. It also contrasts the result with what sibling feed tools give you ('比只看帖子标题可靠'), so the agent can distinguish it without opening the 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?

Gives a clear trigger: after finding app-related 动态, use the package name to check the app itself, specifically to decide identity ('是不是同一个 App') and current version. It lacks an explicit exclusion naming a sibling to avoid, but the usage context is concrete rather than implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.