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
list_meetingsA

List recent meetings with title, date, duration, and participant names.

get_meeting_transcriptA

Get the full transcript for a specific meeting with speaker labels and timestamps.

search_transcriptsA

Search across all meeting transcripts using full-text search. Returns matching segments with meeting context and speaker attribution.

find_speakersA

Look up enrolled speakers by name. Returns candidates with IDs for use with get_speaker_contributions. Only returns speakers with stable cross-meeting identities (not transient per-meeting guests).

get_speaker_contributionsA

Get everything a specific enrolled speaker said across all meetings. Use find_speakers first to get the speaker ID.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing meetings, retrieving a transcript, searching transcripts, finding speakers, and aggregating speaker contributions. There is no functional overlap or ambiguity between tools.

Naming Consistency5/5

All tool names follow the same verb_noun pattern in snake_case (e.g., list_meetings, get_meeting_transcript, search_transcripts), which makes the naming scheme predictable and consistent across the entire set.

Tool Count5/5

Five tools is a well-scoped count for a meeting transcription and speaker analytics server. Each tool covers a distinct functional area without redundancy or excessive granularity.

Completeness5/5

The server provides complete coverage of its core domain: browsing meetings, reading transcripts, full-text search, and per-speaker contribution analysis. There are no obvious gaps or dead ends in the workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues