Skip to main content
Glama

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_mailbox_infoB

Your mailbox address and who you may receive mail from and send mail to.

list_messagesB

List received messages (newest first). Only mail from allowed senders is visible.

read_messageA

Read one message with its body as Markdown. Marks it as read unless mark_read is false.

get_attachmentC

Download an attachment of a message.

mark_messageC

Mark a message as read or unread.

delete_messageB

Move a message to Trash (only if the mailbox allows deleting).

send_messageA

Send an email written in Markdown. Every recipient must be on the allow list. Attachments are base64.

create_eventC

Send a calendar invitation. Times without offset use the given or mailbox time zone.

update_eventA

Change an event you created; attendees get an updated invitation.

cancel_eventB

Cancel an event you created; attendees get a cancellation.

list_eventsC

Events created by this mailbox.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 11 tools

Disambiguation4/5

Tools mostly target distinct resources and actions: messages versus events, and read/list/send/delete are separable. read_message and mark_message overlap slightly around marking messages as read, but the descriptions make selection clear.

Naming Consistency5/5

All tools use snake_case with a consistent verb_noun pattern, such as list_messages, read_message, send_message, create_event, and cancel_event. The naming is predictable throughout.

Tool Count5/5

At 11 tools, the set is well-scoped for an email and calendar gateway. Each tool covers a specific operation without obvious redundancy.

Completeness4/5

The surface covers core email workflows (list/read/send/delete/mark/attachments) and calendar event create/update/cancel/list operations. Minor gaps remain, such as no reply/forward/search for messages and no single-event detail or RSVP handling, but agents can work around them.

Maintenance

ActivityMaintained
ResponsivenessNo issues