snowluma-file-sender
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FILE_SECRETARY_HOME | Yes | Directory where all runtime data, configuration, staged files, and metadata are stored. | |
| ONEBOT_ACCESS_TOKEN | No | Access token for the local OneBot gateway. Optional if the gateway has no authentication enabled; recommended when gateway authentication is available. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| file_secretary_helpA | 本机文件秘书流程。用户要求把文件发给自己时先读此工具。 |
| prepare_fileB | 准备用户指定的文件副本，不发送。返回 deliveryId；收件人由本地配置固定。 |
| send_fileA | 按用户指令发送已准备文件，只传 deliveryId。unknown/sending/busy 禁止自动重发。 |
| delivery_statusA | 查询同一 deliveryId 的本地状态，不发文件；不代表收件方已下载。 |
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 4 tools
Each tool has a clearly distinct role: prepare creates a deliveryId, send_file sends an already prepared file, delivery_status checks local status only, and file_secretary_help documents the workflow. The boundaries between preparation, sending, and status checking are explicit.
All names use snake_case, but the convention is mixed: send_file and prepare_file are verb_noun, while delivery_status and file_secretary_help are noun-based. The names remain readable and reasonably predictable.
Four tools are well-scoped for a narrow file-sending workflow: help, prepare, send, and status. Each tool appears to earn its place without unnecessary surface area.
The set covers the core lifecycle from preparing a file to sending it and checking delivery status, plus workflow help. Minor gaps exist around canceling, listing deliveries, or handling resend/busy cases beyond the documented prohibition.