Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SUPABASE_URLYesThe URL of your Supabase project, e.g. https://your-project-ref.supabase.co
SUPABASE_ANON_KEYYesYour Supabase anon key
SUPABASE_ACCESS_TOKENNoA signed-in user's session token, needed if your RLS policies scope rows to auth.uid(). Without it the server reads whatever the anon role may see.

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
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_songsB

List songs in the band's repertoire, optionally filtered by a title/artist search, musical key, or minimum/maximum BPM.

get_songB

Get one song by id, including its chord chart and rehearsal notes.

list_setlistsC

List setlists, newest first.

get_setlistA

Get one setlist by id with its songs in performance order, grouped by section when sections are used.

list_showsB

List shows (gigs). Filter upcoming/past and by booking status (e.g. Enquiry, Confirmed, Advance Received, Completed).

get_showA

Get one show by id, plus its setlist when one exists.

suggest_songsC

Suggest songs for building a set, filtered by key and/or BPM range. Useful for 'give me upbeat songs in G' style requests.

band_statsA

Quick overview: total songs, setlists, shows, and how many shows are coming up.

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 8 tools

Disambiguation3/5

Most tools have clear resource/action boundaries (list/get for songs, setlists, and shows; band_stats is distinct). However, suggest_songs overlaps substantially with list_songs, since both filter songs by key and BPM range, and the distinction is only loosely clarified as 'for building a set.'

Naming Consistency4/5

The set mostly follows a consistent snake_case verb_noun pattern: list_songs, get_song, list_setlists, get_setlist, list_shows, get_show, and suggest_songs. band_stats is the one deviation, using a noun phrase with no verb, but it is still readable and predictable.

Tool Count5/5

Eight tools is well-scoped for a band repertoire/setlist/show assistant. Each tool covers a clear read-oriented operation, and there is no excessive surface area.

Completeness3/5

The read side is solid: songs, setlists, and shows all have list/get coverage, plus suggestions and stats. However, the surface has no create/update/delete operations for songs, setlists, or shows, and no way to edit setlists or booking status, which are notable gaps for a band management domain.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues