Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DAILY_API_KEYYesYour Daily 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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_user_infoA

Get information about the Daily user account

get_activitiesB

Get list of activities from Daily

get_summaryC

Get time summary for activities within a date range

get_timesheetC

Get detailed timesheet data for a date range

add_activitiesC

Add new activities to Daily

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 5 tools

Disambiguation4/5

Tools are mostly distinct: get_user_info and add_activities are clear, while get_activities, get_summary, and get_timesheet overlap in domain but differ in output (list vs. summary vs. detailed timesheet). Descriptions effectively clarify these boundaries, so confusion is minimal.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_activities, add_activities, get_timesheet). The verbs are limited to 'get' and 'add', which is intuitive for read/write operations, and there are no mixed conventions.

Tool Count5/5

With 5 tools, the server is well-scoped for a time-tracking domain. Each tool covers a core need (user info, activities, summary, timesheet, adding activities) without superfluous or redundant endpoints.

Completeness3/5

The server provides good read coverage (user info, activities, summary, timesheet) and the ability to add activities, but lacks update and delete operations for activities. This is a notable gap for full lifecycle management, as users cannot correct or remove erroneous entries.

Maintenance

ActivityInactive
ResponsivenessNo issues