Skip to main content
Glama
NotoriousArnav

EventHorizon MCP Server

delete_event

Remove an event from the EventHorizon platform. This action is restricted to the event organizer to manage their scheduled activities.

Instructions

Delete an event. Only the organizer can delete their events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesThe ID of the event to delete

Implementation Reference

  • src/index.ts:178-198 (registration)
    Registration of the 'delete_event' MCP tool using server.tool(), including description, input schema, and inline handler function.
    server.tool(
      'delete_event',
      'Delete an event. Only the organizer can delete their events.',
      {
        event_id: z.number().describe('The ID of the event to delete')
      },
      async ({ event_id }) => {
        try {
          const apiClient = getClient();
          await apiClient.deleteEvent(event_id);
          return {
            content: [{ type: 'text', text: `Event ${event_id} deleted successfully.` }]
          };
        } catch (error) {
          return {
            content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
            isError: true
          };
        }
      }
    );
  • The handler function for the 'delete_event' tool. It retrieves the API client, calls deleteEvent on it with the provided event_id, and returns a success or error message.
    async ({ event_id }) => {
      try {
        const apiClient = getClient();
        await apiClient.deleteEvent(event_id);
        return {
          content: [{ type: 'text', text: `Event ${event_id} deleted successfully.` }]
        };
      } catch (error) {
        return {
          content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
          isError: true
        };
      }
    }
  • Zod input schema for the 'delete_event' tool, requiring a single 'event_id' parameter of type number.
    {
      event_id: z.number().describe('The ID of the event to delete')
    },
  • API client method that performs the HTTP DELETE request to remove the event from the backend API.
    async deleteEvent(eventId: number): Promise<void> {
      try {
        await this.client.delete(`/api/events/${eventId}/`);
      } catch (error) {
        throw new Error(`Failed to delete event ${eventId}: ${getErrorMessage(error)}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the authorization constraint ('Only the organizer can delete their events'), which is valuable. However, it doesn't describe whether deletion is permanent/reversible, what happens to associated data (e.g., registrations), error conditions, or response format, leaving significant gaps for a destructive operation.

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

Conciseness5/5

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

The description is two concise sentences that are front-loaded with the core action and immediately followed by the key constraint. Every word earns its place with no redundancy or fluff, making it highly efficient.

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?

For a destructive tool with no annotations and no output schema, the description is minimally adequate. It covers the basic purpose and authorization but lacks details on permanence, side effects, error handling, or return values. Given the complexity of deletion, more context would be helpful for safe agent operation.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already fully documents the 'event_id' parameter. The description doesn't add any parameter-specific information beyond what's in the schema, such as format examples or ID sourcing. This meets the baseline for high schema coverage.

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 action ('Delete') and resource ('an event'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'unregister_from_event' or 'update_event' beyond the core verb, which prevents a perfect score.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('Only the organizer can delete their events'), which helps the agent understand authorization requirements. However, it doesn't explicitly mention when NOT to use it or name alternatives (e.g., using 'update_event' to cancel instead of delete), so it falls short of a 5.

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/NotoriousArnav/EventHorizon-MCP'

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