daily_hot_cache_stats
Retrieve memory cache hit and write statistics to monitor caching performance for daily hot lists from multiple sources.
Instructions
查看内存缓存命中/写入统计。
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Retrieve memory cache hit and write statistics to monitor caching performance for daily hot lists from multiple sources.
查看内存缓存命中/写入统计。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The word '查看' (view) indicates read-only behavior, disclosing non-destructive nature, though no annotations exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short, focused sentence with no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a zero-parameter stats tool, though output format or metric scope could be specified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so baseline 4 applies; description adds no param info, which is acceptable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description '查看内存缓存命中/写入统计' clearly states it is for viewing cache hit/write statistics, distinguishing it from sibling tools like clear, get, and list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when cache statistics are needed, but lacks explicit when-not-to-use or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Micro66/daily-hot-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server