Skip to main content
Glama
ramaiyaKushal

AVA MCP Server

by ramaiyaKushal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
write_email_draftA

Create a draft email using the Gmail API.

Args:
    recipient_email (str): The email address of the recipient.
    subject (str): The subject line of the email.
    body (str): The main content/body of the email.

Returns:
    dict or None: A dictionary containing the draft information including 'id' and 'message' 
                 if successful, None if an error occurs.

Raises:
    HttpError: If there is an error communicating with the Gmail API.
    
Note:
    This function requires:
    - Gmail API credentials to be properly configured
    - USER_EMAIL environment variable to be set with the sender's email address
    - Appropriate Gmail API permissions for creating drafts

Prompts

Interactive templates invoked by user choice

NameDescription
avaGlobal instructions for Artificial Virutal Assistant (AVA)

Resources

Contextual data attached and managed by the client

NameDescription
email-examples://3-way-intro
email-examples://call-follow-up
directory://all
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is singular and clearly defined as creating email drafts via Gmail API.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (write_email_draft). With only one tool, consistency is inherently perfect as there are no other names to compare against.

Tool Count2/5

A single tool is insufficient for an email/Gmail server's scope. Basic email operations like sending, reading, listing, or deleting emails are missing, making this server feel incomplete and thin for its apparent domain.

Completeness2/5

The server is severely incomplete for email management. While write_email_draft covers draft creation, it lacks essential operations like send_email, list_emails, get_email, delete_email, or manage labels, creating significant gaps that will cause agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources