Skip to main content
Glama
abutbul

Gatherings MCP Server

by abutbul

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
create_gatheringC

Create a new gathering

add_expenseC

Add an expense for a member

calculate_reimbursementsC

Calculate reimbursements for a gathering

record_paymentC

Record a payment made by a member

rename_memberC

Rename an unnamed member

show_gatheringC

Show details of a gathering

list_gatheringsC

List all gatherings

close_gatheringC

Close a gathering

delete_gatheringC

Delete a gathering

add_memberC

Add a new member to a gathering

remove_memberC

Remove a member from a gathering

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 11 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: add_expense, add_member, calculate_reimbursements, close_gathering, create_gathering, delete_gathering, list_gatherings, record_payment, remove_member, rename_member, and show_gathering all target specific actions on distinct resources (expenses, members, gatherings, payments). An agent can easily differentiate them without confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, such as add_expense, create_gathering, list_gatherings, and show_gathering. There are no deviations in style or convention, making the set predictable and readable.

Tool Count5/5

With 11 tools, the count is well-scoped for managing gatherings, expenses, members, and payments. Each tool serves a clear purpose (e.g., CRUD operations for gatherings and members, financial actions like expenses and reimbursements), and none feel redundant or unnecessary for the domain.

Completeness4/5

The tool set provides strong coverage for core gathering management workflows, including creation, listing, showing, closing, and deletion of gatherings, as well as member and expense handling. Minor gaps exist, such as no tools for updating gathering details or expenses directly, but agents can work around these by using combinations like rename_member or recreating items.

Maintenance

ActivityInactive
ResponsivenessNo issues