Skip to main content
Glama
coolapk-mcp-pro

coolapk-mcp-pro

by yufeng-liang

coolapk_secondhand

二手交易区动态(想了解某机型二手行情、看出售帖时用)。

Instructions

二手交易区动态(想了解某机型二手行情、看出售帖时用)。

Args: brand: 品牌 ID,0 表示全部;1005=苹果(其余品牌 ID 可先用 coolapk_search 搜到手机话题后按需试) page: 页码,默认 1

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

Input Schema

NameRequiredDescriptionDefault
pageNo
brandNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It implies a read-only listing through "动态," and it adds the useful hint that unknown brand IDs can be resolved via coolapk_search, but it says nothing about result ordering, page-size limits, or what appears when a brand has no listings.

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 purpose is front-loaded in one parenthetical line, followed by a compact Args block. Every sentence earns its place, though the raw docstring formatting ("Args:" with indented continuation) is slightly less clean than prose.

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?

An output schema exists, so return values do not need to be spelled out. Still, with no annotations, for a paginated feed tool, the definition should note roughly how many items a page yields and how to know when to stop paging; that information is absent.

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%, so the description has to compensate, and it largely does: brand is explained as 0 = all and 1005 = Apple, with a discovery strategy for other IDs, and the page meaning matches the schema default. It still does not bound page values or explain how paging terminates.

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 (the secondhand trading area feed) and a concrete use case, which is enough to separate it from siblings like coolapk_search or coolapk_feed_detail. However, it only says "动态" and never states what the feed contains or how it is scoped beyond brand.

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?

It gives clear conditions for use: "when you want to know a model's secondhand market price, or to view sale posts," and it routes the agent to coolapk_search to resolve the brand ID. It does not say when not to use it, and it does not name alternatives for pure lookups, so it stops short of 5.

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