inbox-relay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GMAIL_TOKEN_PATH | No | Path to the token file minted by running the Google OAuth consent flow once. The file is gitignored and never committed. |
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 |
|---|---|
| search_messagesB | Search the inbox (Gmail search syntax). Returns matching message ids. |
| get_messageB | Fetch one message in full: headers, body, and labels. |
| list_threadsB | List inbox threads, optionally filtered by a Gmail search query. |
| list_labelsA | List all Gmail labels with their ids (needed before apply_label). |
| apply_labelA | Label a message AND archive it out of the inbox (reversible). Only call this for high-confidence classifications; unsure messages stay in the inbox. |
| create_draftA | Create a Gmail DRAFT only. The user sends it manually. This never sends. |
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
Most tools target distinct resource+action pairs (search messages, fetch message, list labels, label+archive, draft). The only real overlap is search_messages vs list_threads, since both accept Gmail search queries, but the message-vs-thread distinction and the return shapes are stated clearly enough to pick correctly.
Every tool follows a clean verb_noun snake_case pattern: search_messages, get_message, list_threads, list_labels, apply_label, create_draft. No style mixing or vague verbs.
Six tools is tightly scoped for a triage/relay workflow: search, read, enumerate threads/labels, label-and-archive, and draft. Each tool earns its place with no filler.
Covers the core triage loop (find, read, classify, draft) well. Minor gaps: there is no tool to fetch a full thread (only list_threads) and no way to undo the archive/label despite apply_label being described as reversible, which leaves a potential dead end.