Skip to main content
Glama
highthon-16

MCP Calendar Server

by highthon-16

get_all_events

Retrieve all calendar events from the MCP Calendar Server to view and manage your schedule. This tool fetches every event across all categories for comprehensive oversight.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler function for 'get_all_events', decorated with @mcp.tool() which also serves as registration. It fetches all events for the default user via CalendarService and converts them to response objects.
    @mcp.tool()
    def get_all_events() -> List[CalendarEventResponse]:
        """
        모든 캘린더 이벤트를 조회합니다.
        """
        try:
            result = calendar_service.fetch_events(DEFAULT_USER_ID)
            if result.success and result.data:
                return [calendar_service.to_response(event) for event in result.data]
            return []
        except Exception as e:
            raise Exception(f"이벤트 조회 중 오류가 발생했습니다: {str(e)}")
  • Pydantic model defining the schema for individual CalendarEventResponse objects returned by get_all_events (as a list). Includes serialization for datetime fields.
    class CalendarEventResponse(BaseModel):
        """캘린더 이벤트 응답"""
        id: int
        title: str
        description: Optional[str] = None
        location: Optional[str] = None
        start_time: datetime
        duration: int
        category: EventCategory
        stamina_cost: int
        status: EventStatus
        stamina_after_completion: Optional[int] = None
        created_at: datetime
    
        @field_serializer('start_time', 'created_at')
        def serialize_datetime(self, value: datetime) -> str:
            return value.isoformat()
    class ApiResponse(BaseModel):
  • Core helper method in CalendarService that retrieves all events for a given user_id from the in-memory database, used by the tool handler.
    def fetch_events(self, user_id: int) -> McpResult:
        """사용자의 모든 이벤트 조회"""
        try:
            user_events = [
                event for event in self.events_db.values() 
                if event.user_id == user_id
            ]
            return McpResult(success=True, data=user_events)
        except Exception as e:
            return McpResult(success=False, error=str(e))
  • Helper method to convert internal CalendarEvent entities to the public CalendarEventResponse schema used by the tool.
    def to_response(self, event: CalendarEvent) -> CalendarEventResponse:
        """Entity를 Response로 변환"""
        return CalendarEventResponse(
            id=event.id,
            title=event.title,
            description=event.description,
            location=event.location,
            start_time=event.start_time,
            duration=event.duration,
            category=event.category,
            stamina_cost=event.stamina_cost,
            status=event.status,
            stamina_after_completion=event.stamina_after_completion,
            created_at=event.created_at
        )
  • Enum schema for event categories, used in CalendarEventResponse.
    class EventCategory(str, Enum):
        """이벤트 카테고리"""
        STUDY = "STUDY"      # 학습
        WORK = "WORK"        # 업무
        REST = "REST"        # 휴식
        ACTIVITY = "ACTIVITY" # 활동
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states retrieval but doesn't disclose behavioral traits like whether this requires authentication, returns paginated results, includes deleted events, or has rate limits. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in Korean that directly states the action. It's appropriately sized for a simple tool, with no wasted words, though it could be more front-loaded with differentiation from siblings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (0 parameters, read-only operation) and the presence of an output schema, the description is minimally adequate. However, with no annotations and multiple sibling tools, it lacks context on when to use it versus alternatives, leaving room for improvement in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. Baseline is 4 for zero parameters, as there's nothing to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '모든 캘린더 이벤트를 조회합니다' (Retrieves all calendar events) clearly states the verb (retrieve) and resource (calendar events), establishing basic purpose. However, it doesn't differentiate from siblings like get_event_by_id or get_events_by_date, which are more specific retrieval tools. The description is accurate but generic.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With siblings like get_events_by_date for date-filtered retrieval or get_event_by_id for single events, there's no indication that this tool returns unfiltered/all events, leaving usage context implied at best.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/highthon-16/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server