Skip to main content
Glama
highthon-16

MCP Calendar Server

by highthon-16

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_all_eventsC

모든 캘린더 이벤트를 조회합니다.

get_event_by_idB

ID로 특정 캘린더 이벤트를 조회합니다.

create_calendar_eventA
새로운 캘린더 이벤트를 생성합니다.

Args:
    title: 이벤트 제목
    start_time: 시작 시간 (ISO 형식: 2025-08-02T10:00:00)
    duration: 지속 시간(분)
    category: 카테고리 (STUDY, WORK, REST, ACTIVITY)
    description: 이벤트 설명 (선택)
    location: 장소 (선택)
    stamina_cost: 스태미나 소모량 (기본값: 0)
update_calendar_eventB
기존 캘린더 이벤트를 수정합니다.

Args:
    event_id: 수정할 이벤트 ID
    title: 이벤트 제목
    start_time: 시작 시간 (ISO 형식: 2025-08-02T10:00:00)
    duration: 지속 시간(분)
    category: 카테고리 (STUDY, WORK, REST, ACTIVITY)
    description: 이벤트 설명 (선택)
    location: 장소 (선택)
    stamina_cost: 스태미나 소모량 (기본값: 0)
    status: 이벤트 상태 (PLANNED, COMPLETED, CANCELED) (선택)
delete_calendar_eventB
캘린더 이벤트를 삭제합니다.

Args:
    event_id: 삭제할 이벤트 ID
complete_eventB
이벤트를 완료 상태로 변경하고 완료 후 스태미나를 설정합니다.

Args:
    event_id: 완료할 이벤트 ID
    stamina_after: 완료 후 스태미나 수치
get_events_by_categoryB
카테고리별로 이벤트를 조회합니다.

Args:
    category: 카테고리 (STUDY, WORK, REST, ACTIVITY)
get_events_by_dateB
특정 날짜의 이벤트를 조회합니다.

Args:
    date: 날짜 (YYYY-MM-DD 형식)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. The CRUD operations (create, get, update, delete) target different actions, while the query tools (get_all_events, get_events_by_category, get_events_by_date) provide complementary filtering options. The complete_event tool uniquely handles event completion with stamina management, separate from general updates.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (create_calendar_event, delete_calendar_event, update_calendar_event, get_all_events, get_event_by_id, get_events_by_category, get_events_by_date). The only deviation is complete_event, which uses a different verb style and omits the 'calendar' prefix, but this is minor given its distinct functionality.

Tool Count5/5

With 8 tools, this server is well-scoped for calendar management. It provides full CRUD operations plus specialized queries and a unique completion tool, avoiding both under-coverage (e.g., just 1-2 tools) and bloat (e.g., 25+ tools). Each tool earns its place in the workflow.

Completeness5/5

The toolset offers complete coverage for calendar event management: create, read (with multiple query options), update, and delete operations. It also includes specialized functionality like event completion with stamina tracking and status management. No obvious gaps exist for the domain, supporting full agent workflows without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues