Skip to main content
Glama
xiaobenyang-com

Realtime-News

hupu_a_news

hupu_a_news

Access real-time trending topics from Hupu Walking Street's hot list to monitor current discussions and popular content.

Instructions

实时数据/虎扑步行街热榜A

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions '实时数据' (real-time data) which implies freshness, but doesn't disclose behavioral traits like rate limits, authentication needs, data format, or whether this is a read-only operation. For a tool with zero annotation coverage, this is inadequate.

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 description is extremely concise—just two Chinese phrases separated by a slash. While efficient, it might be too terse given the lack of differentiation from sibling tools. Every word earns its place, but more structure could improve clarity.

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 the complexity of news data tools and lack of both annotations and output schema, the description is incomplete. It doesn't explain what '热榜A' means, what data format to expect, or how this differs from other Hupu tools. For a tool in a crowded namespace, more context is needed.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter information, but that's appropriate given the empty schema. Baseline for 0 parameters is 4.

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 '实时数据/虎扑步行街热榜A' states the tool provides real-time data from Hupu's '步行街' hot list A, which is a specific resource. However, it doesn't clearly distinguish from sibling tools like 'hupu_news'—the 'A' designation is ambiguous without explanation of what differentiates this from other Hupu news 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 is provided on when to use this tool versus alternatives. With multiple sibling tools including 'hupu_news', there's no indication of whether this tool provides different content, format, or scope. The description offers no context about use cases or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xiaobenyang-com/1804087353852938'

If you have feedback or need assistance with the MCP directory API, please join our Discord server