stepwork-hotspot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sourcesA | 列出可用热点源（形态、是否需密钥、实测备注） |
| discover_hotspotsA | 抓取热点条目：按时间窗过滤、跨源去重、按时间/热度排序。某个源失败不会让整个调用失败，但会列在 errors 里。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one enumerates available sources with metadata, the other fetches actual hotspot entries with filtering and deduplication. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun pattern (list_sources, discover_hotspots), using snake_case and clear action-resource structure. The naming is predictable and uniform.
With only two tools, the server feels thin for a domain that might benefit from additional operations like source management or detailed retrieval. However, the two tools cover a focused workflow, making it borderline rather than severely under-scoped.
The core workflow of discovering hotspots from listed sources is covered. Minor gaps exist, such as the lack of tools to modify sources or fetch individual hotspot details, but these are not critical for the primary use case.