l2calendar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| L2CALENDAR_API_URL | No | Base URL of the L2 Calendar instance to query. | https://l2calendar.com |
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 |
|---|---|
| list_serversA | List Lineage 2 private servers tracked by L2 Calendar, ordered by VIP status and opening date. Optionally filter by chronicle, upcoming openings, newly added entries or rate range. |
| get_chroniclesA | List every Lineage 2 chronicle tracked by L2 Calendar (slug, display name and order). Use the slugs as the chronicle filter for list_servers. |
| search_serversA | Search the current L2 Calendar server page by free text. Matches the server name, website, rate, chronicle, description and labels (case-insensitive). |
| get_serverA | Return the full public record of a single server by its exact name (case-insensitive), including description and labels. |
| list_labelsA | List the distinct labels (e.g. PTS, Low rate, Craft) currently applied to servers on the public page, with their colors. |
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 5 tools
Most tools have clearly distinct purposes, with list_servers, search_servers, and get_server each serving different retrieval modes. The only possible confusion is between list_servers and search_servers, since both return servers, but their filtering vs. free-text search approaches are described distinctly.
All tool names follow a consistent snake_case verb_noun pattern: list_servers, get_chronicles, search_servers, get_server, list_labels. The verbs (list, get, search) are predictable and match the action each tool performs.
Five tools is a well-scoped set for a read-only calendar/lookup service. Each tool covers a distinct need—listing, searching, detail retrieval, and reference lookups—without unnecessary redundancy or bloat.
The tool surface fully covers the apparent read-only domain: broad listing with filters, free-text search, exact record retrieval, and enumeration of chronicles and labels. No obvious dead ends or missing operations for the stated purpose.