Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WORK_WINDOW_RESET_ATNoOptional ISO 8601 timestamp for the next quota reset time. Used in demo and available for configuration.
WORK_WINDOW_QUOTA_PERCENTYesThe quota percentage for the work window. Required for v0.1; the MCP server process must receive this environment variable. Do not present manual-provider values as real Codex readings.

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
window_planC

Turn current quota into a bounded work segment with reserve and checkpoint rules.

checkpoint_saveB

Save a bounded, redacted handoff state for deterministic resume.

resume_contractC

Prepare a resume contract from the last checkpoint and current capacity.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct phase of the work-window lifecycle: planning rules, saving state, and preparing a resume contract. There is no functional overlap or ambiguity about which tool to call.

Naming Consistency4/5

All names use a two-word underscore convention and clearly describe their action, but the pattern is mixed: window_plan and checkpoint_save are noun-verb while resume_contract is verb-noun. This is a minor deviation from a strictly consistent verb_noun scheme.

Tool Count5/5

Three tools is well-scoped for a focused workflow around planning, saving, and resuming work windows. Each tool earns a clear place; nothing feels redundant or missing at the surface level.

Completeness4/5

The set covers the core lifecycle of a work window: planning, checkpointing, and resuming. Minor gaps exist such as an explicit finalize/cancel action, but agents can work around those by planning a new window or not resuming.

Maintenance

ActivityMaintained
ResponsivenessNo issues