Skip to main content
Glama
highthon-16

MCP Calendar Server

by highthon-16

delete_calendar_event

Remove calendar events by specifying the event ID to manage your schedule and keep it organized.

Instructions

캘린더 이벤트를 삭제합니다.

Args:
    event_id: 삭제할 이벤트 ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function decorated with @mcp.tool(). Handles deletion by calling CalendarService.delete_event and returns success/error message.
    @mcp.tool()
    def delete_calendar_event(event_id: int) -> str:
        """
        캘린더 이벤트를 삭제합니다.
        
        Args:
            event_id: 삭제할 이벤트 ID
        """
        try:
            result = calendar_service.delete_event(event_id, DEFAULT_USER_ID)
            if result.success:
                return f"이벤트 ID {event_id}가 성공적으로 삭제되었습니다"
            
            raise Exception(result.error or "이벤트 삭제에 실패했습니다")
            
        except CalendarException:
            raise
        except Exception as e:
            raise Exception(f"이벤트 삭제 중 오류가 발생했습니다: {str(e)}")
  • Core service method that performs the actual deletion from the in-memory events database after existence and authorization checks.
    def delete_event(self, event_id: int, user_id: int) -> McpResult:
        """이벤트 삭제"""
        try:
            if event_id not in self.events_db:
                raise EventNotFound(event_id)
            
            existing_event = self.events_db[event_id]
            if existing_event.user_id != user_id:
                raise UnauthorizedAccess(user_id, event_id)
            
            del self.events_db[event_id]
            return McpResult(success=True, data=None)
            
        except CalendarException:
            raise
        except Exception as e:
            return McpResult(success=False, error=str(e))
  • src/main.py:180-198 (registration)
    The @mcp.tool() decorator registers this function as an MCP tool.
    @mcp.tool()
    def delete_calendar_event(event_id: int) -> str:
        """
        캘린더 이벤트를 삭제합니다.
        
        Args:
            event_id: 삭제할 이벤트 ID
        """
        try:
            result = calendar_service.delete_event(event_id, DEFAULT_USER_ID)
            if result.success:
                return f"이벤트 ID {event_id}가 성공적으로 삭제되었습니다"
            
            raise Exception(result.error or "이벤트 삭제에 실패했습니다")
            
        except CalendarException:
            raise
        except Exception as e:
            raise Exception(f"이벤트 삭제 중 오류가 발생했습니다: {str(e)}")
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('delete') but doesn't specify whether this is a permanent deletion, if it requires specific permissions, what happens to related data, or any rate limits. For a destructive operation with zero annotation coverage, this leaves critical behavioral traits unaddressed.

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 appropriately sized and front-loaded, with the core purpose stated first in a clear sentence. The parameter explanation is concise and directly relevant. However, the structure could be slightly improved by integrating the parameter info more seamlessly rather than as a separate 'Args' section.

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 complexity (destructive operation with no annotations) and the presence of an output schema (which handles return values), the description is minimally adequate. It covers the basic purpose and parameter but lacks details on behavioral aspects like permissions, reversibility, or error handling, which are important for such a tool.

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 description adds meaningful context for the single parameter 'event_id' by specifying it as '삭제할 이벤트 ID' (event ID to delete), which clarifies its role beyond what the schema provides (just 'Event Id' with type integer). With 0% schema description coverage and only one parameter, this compensates adequately, though it doesn't detail format or sourcing of the ID.

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

Purpose4/5

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

The description clearly states the verb ('delete') and resource ('calendar event'), making the purpose immediately understandable. It distinguishes itself from siblings like 'create_calendar_event' and 'update_calendar_event' by specifying deletion rather than creation or modification. However, it doesn't explicitly differentiate from other destructive operations like 'complete_event'.

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. It doesn't mention prerequisites (e.g., needing an existing event ID), when not to use it (e.g., for soft deletion vs. hard deletion), or direct alternatives among siblings like 'complete_event' which might serve a similar purpose in some contexts.

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