Skip to main content
Glama
Sign In
dailyhot

dailyhot

by FrankXMX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

百度

baidu

Retrieve trending topics from Baidu's hot search list to identify current popular 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": "baidu"
  }
}

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, so the description must carry the full burden. It does not mention any behavioral traits such as authentication requirements, rate limits, or whether the operation is read-only. The description is minimal.

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 essential details. It is not structured to aid quick understanding.

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 presence of many sibling tools and no output schema, the description should provide more context about the returned data (e.g., format, fields). It is insufficient for an agent to select or invoke reliably.

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 tool description does not explain the 'limit' or 'noCache' parameters. An agent would not know their meaning or default values (except from schema defaults).

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 states the tool's action ('获取' meaning 'get') and resource ('百度热搜榜数据' meaning 'Baidu hot search list data'). It distinguishes from siblings by being specific to Baidu, but does not explicitly differentiate beyond the resource name.

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 like 'weibo' or 'zhihu'. The description only states what it does without context or exclusions.

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