Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MG_API_KEYYesAn API key from mg.robnugen.com/settings/

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
start_sessionA

Start a new behavioral session. Costs 1 credit.

The server records the current time automatically — the agent does not
need to track time. Returns the new session including its ak_id, which
you need to stop or check the session later.

Args:
    activity_id: Activity type ID (default 1 = Meditation).
                 Use list_activities to see all options.
    timezone: IANA timezone name, e.g. 'Asia/Tokyo' (default UTC).
    intended_sec: Planned duration in seconds (default 0 = open-ended).
stop_sessionA

Stop an active session. Free (0 credits).

The server computes actual_sec automatically using the stored start time.
The agent does not need to track elapsed time.

Args:
    ak_id: The session ID returned by start_session.
check_sessionA

Get details for a single session, including elapsed_sec if active. Free (0 credits).

Args:
    ak_id: The session ID to look up.
list_sessionsA

List completed and active sessions. Free (0 credits).

Args:
    from_date: Start date filter in YYYY-MM-DD format (optional).
    to_date: End date filter in YYYY-MM-DD format (optional).
    activity_id: Filter by activity type ID (optional, 0 = no filter).
    limit: Number of results to return (default 20, max 50).
    offset: Pagination offset (default 0).
get_statsA

Get pre-computed session aggregates. Costs 1 credit.

Returns total sessions, total seconds, current streak in days, and credits remaining. Offloads all calendar arithmetic to the server.

list_activitiesB

List available activity types (FREE, PUBLIC, and your PRIVATE). Free (0 credits).

create_activityA

Create a custom PRIVATE activity visible only to your account. Free (0 credits).

Args:
    activity_name: Name for the new activity (max 64 characters).
    description: Optional description of the activity.

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.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: check_session retrieves details for a single session, create_activity creates a private activity, get_stats provides aggregate statistics, list_activities and list_sessions handle listing with different scopes, start_session initiates a session, and stop_session ends one. The descriptions reinforce these distinct roles, making tool selection unambiguous.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case: check_session, create_activity, get_stats, list_activities, list_sessions, start_session, and stop_session. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.

Tool Count5/5

With 7 tools, the server is well-scoped for its apparent purpose of tracking behavioral sessions and activities. Each tool serves a specific function in the lifecycle (e.g., create, list, start, stop, check), and none feel redundant or missing, fitting within the ideal 3-15 tool range for such a domain.

Completeness5/5

The tool set provides complete CRUD/lifecycle coverage for session and activity management: create_activity for creation, list_activities and list_sessions for reading, start_session and stop_session for session control, check_session for detailed retrieval, and get_stats for analytics. There are no obvious gaps, ensuring agents can handle all core workflows without dead ends.

Maintenance

ActivityInactive
ResponsivenessUnresponsive