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_commitmentsA

Open promises from recorded meetings, newest first, in two lists: 'mine' (what the user owes) and 'waiting_on_others' (what others owe the user); finished ones are left out. Use for "what do I owe", "what is overdue", "what is Anna still waiting on". For one colleague's whole picture use get_person; to get a name's exact spelling first, list_people.

get_personA

Everything known about one colleague: notes, email addresses, their open promises, and the last recorded meeting with them. Accepts a name or email in any spelling; if nobody matches, returns the known names.

search_meetingsA

Find recorded meetings by title or text, optionally with one participant, newest first. Returns id, title, date, participants and summary — never the transcript. Use the id with get_meeting or get_transcript.

get_meetingA

One meeting by id: summary, participants and the promises made in it. Does not include the transcript; use get_transcript for what was said.

get_transcriptA

The full transcript of one meeting: everything said, including remarks in passing. Long and sensitive; call it only when get_meeting's summary is not enough.

get_next_meeting_briefA

Prep for the user's next calendar meeting: attendees, what each side promised the other, and what was discussed last time. Built from the calendar and recorded meetings; returns available=false with a reason when no meeting is coming up. Use before a call; for a meeting that already happened use search_meetings and get_meeting.

list_upcoming_meetingsA

The user's calendar meetings in the next days, soonest first, each with its attendees and the open promises between the user and them: what the user promised them and what they promised the user. Use for "what's my week", "what do I owe the people I'm meeting". Only events with other people or a call link; all-day events are left out. Needs calendar access; returns available=false with a reason without it. For the very next call in detail, get_next_meeting_brief.

draft_followupA

A follow-up email for one meeting, written from Griasa's notes: the summary and who promised what for all participants, or, with person, only what that person and the user promised. Returns subject, body, the addresses Griasa knows and a mailto link. Griasa sends nothing: hand the link to the user or send the draft with the user's own mail tool after they confirm. Meeting id from search_meetings.

list_peopleA

Everyone Griasa knows by name, with how many of their promises are still open. Use to find the exact spelling before get_person or list_commitments.

list_projectsA

List every project the user files recordings and notes under, with id and name, in the order the user keeps them in Settings; unfiled items sit in an Inbox that is not listed. Use to answer what the user is working on or to match a meeting to a project; pass an id as project to search_meetings or list_commitments.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct object or action: meetings, transcripts, people, commitments, calendar, projects, and follow-up drafting are clearly separated. Adjacent tools such as list_upcoming_meetings and get_next_meeting_brief overlap slightly, but the descriptions explicitly redirect between them, leaving little room for misselection.

Naming Consistency5/5

All tool names use snake_case with a consistent verb_noun pattern: get_*, list_*, search_*, and draft_*. Longer names like get_next_meeting_brief and list_upcoming_meetings remain predictable and readable.

Tool Count5/5

Ten tools is well-scoped for a meeting and commitment assistant, with no obvious filler. Each tool covers a meaningful query or drafting workflow.

Completeness4/5

The surface covers meeting lookup, transcripts, people, commitments, calendar prep, projects, and follow-up drafting comprehensively for a read-oriented assistant. Minor gaps remain around commitment lifecycle operations and detailed project retrieval, but agents can mostly work around them via existing search and list tools.

Maintenance

ActivityActive
ResponsivenessNo issues