Skip to main content
Glama
naumanpathan

FathomBridge

by naumanpathan

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FATHOM_API_KEYYesYour Fathom API key

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_meetingsB

List your Fathom meetings with optional date, team, and pagination filters

get_transcriptA

Get the full speaker-labelled, timestamped transcript for a meeting

get_summaryB

Get the AI-generated summary, key points, and action items for a meeting

search_meetingsB

Search meetings by title, host name, or participant email

get_action_itemsA

Get only the action items from a meeting — clean list with owners and due dates

list_teamsA

List all teams in your Fathom organization

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 6 tools

Disambiguation4/5

list_meetings and search_meetings both return meetings but are differentiated by filtering/browsing versus searching by text fields. get_summary and get_action_items overlap slightly since summaries include action items, but the dedicated action-item tool has a clear distinct purpose.

Naming Consistency5/5

All tool names consistently follow a verb_noun snake_case pattern using list, get, or search verbs. There are no mixed conventions or vague generic names.

Tool Count5/5

Six tools is a well-scoped count for a meeting-insights server. Each tool covers a distinct retrieval need without unnecessary bloat or missing core functions.

Completeness4/5

The server covers core read-only workflows: discovering meetings, searching, retrieving transcripts, summaries, action items, and listing teams. A minor gap is the lack of a dedicated get_meeting endpoint for single-meeting metadata, but list_meetings likely covers that need.

Maintenance

ActivityInactive
ResponsivenessNo issues