Skip to main content
Glama
Sign In
dailyhot

dailyhot

by FrankXMX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

YY

yystv

Retrieve hot trending items from YY platform. Fetch real-time popular content for analysis or display.

Instructions

获取YY热榜

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

Input Schema

NameRequiredDescriptionDefault
limitNo
noCacheNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

C2.2/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as caching, rate limits, authentication requirements, or how the 'noCache' parameter affects behavior. The description is purely functional.

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 concise at one sentence, but it is under-specified. It could be restructured to include parameter details or usage hints without becoming 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, no annotations, and two parameters, the description is insufficient. It does not explain the format of the hot list, how parameters affect results, or any prerequisites.

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?

Schema description coverage is 0%, and the description does not mention either 'limit' or 'noCache'. The parameters' meanings and usage are entirely left to the schema with no additional context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '获取YY热榜' indicates the tool retrieves a hot list from YY, which is a platform among many siblings. It states the action and resource but does not clarify what YY is or differentiate from other similar sibling tools.

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 on when to use this tool versus alternatives. The sibling tools are all hot list retrieval tools for different platforms, but the description provides no context for selection.

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