Skip to main content
Glama
Sign In
dailyhot

dailyhot

by FrankXMX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

少数派

sspai

Retrieve hot trending data from ssPai platform. Specify the number of results and choose to bypass cache for fresh content.

Instructions

获取少数派热榜数据

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

Input Schema

NameRequiredDescriptionDefault
limitNo
noCacheNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as caching behavior, rate limits, or authentication requirements. The description adds no behavioral context beyond the name.

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 description is a single short sentence, which is concise but lacks structure. It could be expanded to include parameter details or usage notes without becoming overly verbose.

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

Completeness2/5

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

Given no output schema and two parameters, the description is incomplete. It does not hint at the output format, pagination, or caching behavior, leaving the agent with insufficient information for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain the two parameters (limit, noCache). With 0% schema description coverage, the description carries the full burden, and it fails to provide any meaning for the parameters.

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 '获取少数派热榜数据' clearly indicates the verb (get) and resource (Shaoshupai hot list data), which distinguishes it from sibling tools targeting different platforms. However, it could be more specific about what the hot list contains (e.g., articles, topics).

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?

No guidance is provided on when to use this tool versus alternatives. The description only states what it does, without any context about prerequisites, limitations, or when not to use it.

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