Skip to main content
Glama
Sign In
mcp-quiver

mcp-quiver

by thsrite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_hot_boards

Discover all available hot boards across platforms, showing platform names, board names, and entry counts. Use this to find which websites are supported before searching hot topics.

Instructions

列出全网热榜里所有可用的榜单（平台名 + 榜单名 + 条目数），供 search_hot_topics 的 platform 参数使用。

当用户问"能查哪些网站/平台"，或你不确定某平台在不在覆盖范围内时，先调这个。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It discloses that the tool enumerates all available boards and that the result is meant to seed search_hot_topics' platform parameter. It does not explicitly state side-effect or rate-limit behavior, but an empty-parameter listing tool is clearly read-oriented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler; the core purpose and output shape come first, followed by when-to-use guidance. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter listing tool with an output schema, the description fully covers what the tool returns, how it relates to search_hot_topics, and when to invoke it. Nothing essential is missing.

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?

The input schema has zero parameters, so there is no schema burden and the baseline is 4. The description adds useful cross-tool context by linking the returned boards to search_hot_topics' platform parameter, though it does not need to explain any local parameters.

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 action (列出) on a concrete resource (全网热榜里所有可用的榜单) and specifies the output fields: platform name, board name, and entry count. It also positions the tool as the source for search_hot_topics' platform parameter, making it easy to distinguish from the searching siblings.

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

Usage Guidelines5/5

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

Gives explicit triggers: call it when the user asks which sites/platforms are queryable or when coverage is uncertain. This directly tells the agent when to use list_hot_boards instead of guessing or calling search_hot_topics.

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

Deploy Server

Other Tools