countdowns-online-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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_countdown_overviewA | Return the canonical countdown categories, verified date semantics, and public entry points exposed by the site. (Countdowns Online) |
| get_official_linksA | Return the canonical list of official links for Countdowns Online (website, support, docs when available). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tell_me_about_countdowns_online | Summarize what the site is, who it's for, and how it works. — Countdowns Online |
| choose_a_countdown_countdowns_online | Choose a countdown while respecting date verification and regional timing. — Countdowns Online |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| events | Verified event dates, recurrence rules, regional timing semantics, and custom countdown entry points. |
| faq | Short FAQ generated from public site metadata. |
| links | Canonical URLs to share with users. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_countdown_overview provides an overview of countdown categories and dates, while get_official_links returns official website links. There is no overlap or ambiguity.
Both tools follow the same 'get_' prefix and snake_case naming pattern, resulting in a consistent and predictable naming convention.
With only 2 tools, the server feels minimal. While it may serve a narrow purpose, the count is low for a typical MCP server, limiting its utility.
The tool surface covers only overview and link retrieval, lacking any actionable operations (e.g., listing or managing countdowns). This leaves significant gaps for interacting with the domain.