AVA
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USER_EMAIL | Yes | Your Gmail email address | |
| GOOGLE_TOKEN_PATH | Yes | Path to the stored OAuth2 token JSON file | |
| GOOGLE_CREDENTIALS_PATH | Yes | Path to the OAuth2 client credentials JSON file |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write_email_draftC | Create a Gmail draft using recipient, subject, and body. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap. The purpose is uniquely defined.
The single tool name 'write_email_draft' follows a clear verb_noun pattern, demonstrating internal consistency.
A single tool is borderline; while it performs a concrete task, the server feels overly thin for anything beyond a very narrow use case.
The tool only creates a draft with no support for listing, updating, deleting, or sending, leaving significant gaps in email management.