Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TOGGL_API_KEYYesYour Toggl API key. Get it from https://track.toggl.com/profile by scrolling down to 'API Token' and clicking 'Click to reveal'

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
toggl_startB

Start a new time tracking entry

toggl_stopB

Stop the currently running timer

toggl_currentA

Get the currently running time entry

toggl_todayB

Get today's time entries with total duration

toggl_projectsB

List all projects in the workspace

toggl_deleteC

Delete a time entry by ID

toggl_weeklyC

Get weekly time tracking summary with total hours, daily/project breakdowns

toggl_last_weekB

Get last week's time tracking summary

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity: toggl_current and toggl_stop handle the active timer, toggl_start initiates tracking, toggl_delete removes entries, and the summary tools (toggl_today, toggl_last_week, toggl_weekly) provide different timeframes. The tools toggl_projects stands alone for workspace management. There is no overlap in functionality that would cause misselection.

Naming Consistency5/5

All tools follow a consistent 'toggl_verb' or 'toggl_noun' pattern with clear, descriptive names. The naming is uniform across all eight tools, using lowercase with underscores, making it predictable and easy to understand. There are no deviations in style or convention.

Tool Count5/5

With 8 tools, the server is well-scoped for time tracking and project management. Each tool earns its place by covering essential operations like starting/stopping timers, viewing summaries, managing entries, and listing projects. This count is neither too sparse nor overwhelming for the domain.

Completeness4/5

The tool set provides strong coverage for core time tracking workflows, including CRUD operations (create via toggl_start, read via summary tools, delete via toggl_delete) and project listing. A minor gap exists in updating time entries (e.g., modifying descriptions or projects), but agents can work around this by deleting and recreating entries. Overall, it supports most common user actions without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues