Kaze Feed
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KAZE_FEED_DATA_DIR | No | 指定数据目录；直接运行默认使用用户目录下的 .kaze-feed。 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| feed_manageB | 管理 RSS/Atom 订阅：list、subscribe、unsubscribe、pause、resume。 URL 必须是 HTTP/HTTPS RSS 或 Atom 地址。删除和暂停使用精确名称或 source_id。 订阅后用 poll_feeds 采集，不会自动推送消息。 |
| feed_queryA | 查询已缓存的订阅内容：latest、search、summary、sources、catalog。 查询不触发网络采集。需要刷新时先调用 poll_feeds，并检查失败来源。 返回标题、摘要、原文、发布时间及稳定 event_id。 |
| poll_feedsA | 采集到期 RSS/Atom 来源，每次最多四个，按上次采集时间轮换。 force=true 忽略采集间隔。返回 ok、failed、remaining 和每个来源的结果。 remaining>0 时可继续调用；失败时保留旧缓存并记录原因。 |
| get_proactive_eventsA | 读取最近 36 小时内尚未被此 consumer 消费的候选内容。 不采集、不发送消息、不自动 ACK。consumer 应使用目标会话的 session_key。 |
| acknowledge_eventsA | 记录条目已处理、已读、已丢弃或已送达：processed、read、discarded、delivered。 默认永久消费，ttl_hours 为正数时可在到期后重新出现。 delivered 必须提供宿主真实送达回执 delivery_ref；本服务不验证回执真实性。 准备推送或发送失败都不能标记为已送达。未知 ID 单独返回 missing。 |
| feed_statusC | 查看来源的最近采集时间、成功时间、失败原因和缓存条数。 |
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 6 tools
Each tool targets a distinct phase of the feed lifecycle: manage subscriptions, query cache, poll sources, read proactive events, acknowledge events, and check status. Slight overlap exists between feed_query (latest) and get_proactive_events for reading content, but the consumer/session_key workflow and explicit no-collect/no-send semantics differentiate them.
All names use snake_case, but the prefix/style is mixed: feed_manage, feed_query, and feed_status use a noun-first pattern, while poll_feeds, get_proactive_events, and acknowledge_events are verb-first. The set is readable but lacks a single predictable convention.
Six tools is well-scoped for an RSS/Atom feed and event-consumption server. Each tool has a clear, non-redundant purpose, and no tool feels trivial or out of place.
The surface covers subscription CRUD (subscribe, list, unsubscribe, pause, resume), polling, querying cached content, proactive event retrieval, acknowledgement, and status. Minor gaps exist, such as fetching a single event by ID or bulk acknowledgement, but core workflows are complete.