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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
create_garmin_workoutB

Create a workout in Garmin Connect from structured workout data. Claude should parse the natural language description and pass structured workout steps.

check_garmin_authB

Check if Garmin authentication is valid

authenticate_garminB

Authenticate with Garmin Connect (opens browser)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: authentication initiation, authentication status verification, and workout creation. There is no overlap in functionality, and an agent can easily differentiate between them based on their names and descriptions.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with 'garmin' as a prefix: authenticate_garmin, check_garmin_auth, create_garmin_workout. The naming is uniform and predictable across the set.

Tool Count3/5

With only 3 tools, the set feels thin for a workout management server. While authentication and creation are covered, there are likely gaps such as retrieving, updating, or deleting workouts, which are common operations in this domain.

Completeness2/5

The tool surface is significantly incomplete for workout management. It lacks essential operations like getting existing workouts, updating workouts, deleting workouts, or listing workouts, which are critical for a full CRUD lifecycle. Agents will face dead ends when trying to manage workouts beyond creation.

Maintenance

ActivityInactive
ResponsivenessNo issues