at-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_timerA | Start a timer at the beginning of a task with a user-requested minimum duration. Convert the duration to whole seconds, rounding up (30 minutes = 1800). Preserve timer_id and min_seconds in task context and summaries. Each call creates a new timer; reuse the existing timer for the same task, including after status questions and context compaction. |
| check_timerA | Check the saved timer after long tool calls, at phase changes, and immediately before a completion response. Require both the current minimum duration and task completion. minimum_met refers to the original min_seconds; if the user revises the minimum, compare elapsed_seconds with the revised duration rounded up to whole seconds, using the same timer. Continue useful work within task scope until both conditions are met; avoid idle waiting, rapid polling, redundant tests, and unrelated changes. Progress updates are allowed. Honor explicit stop requests immediately. Errors do not establish elapsed time; recover if possible or report the limitation without claiming completion. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
start_timer and check_timer have clearly distinct actions: one creates a timer, the other inspects an existing timer. The descriptions reinforce this separation, leaving no ambiguity about which tool to use.
Both tool names follow a consistent snake_case verb_noun pattern: start_timer and check_timer. This predictable convention makes the set easy to scan and use.
Two tools is borderline thin for a timer-related server, as there is no explicit stop, reset, pause, or list operation. The pair is coherent, but the surface feels minimal for the apparent domain.
The set covers starting and checking a timer but lacks an explicit stop/delete/reset tool, which is a notable lifecycle gap. The description mentions honoring stop requests, but there is no dedicated tool to perform that operation.