Skip to main content
Glama
NotoriousArnav

EventHorizon MCP Server

create_event

Create new events by specifying title, description, times, location, and capacity for event management and scheduling.

Instructions

Create a new event. Requires title, description, start/end times, location, and capacity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the event
descriptionYesDescription of the event
start_timeYesStart time in ISO 8601 format (e.g., 2024-12-25T10:00:00Z)
end_timeYesEnd time in ISO 8601 format (e.g., 2024-12-25T18:00:00Z)
locationYesLocation of the event
capacityYesMaximum number of attendees

Implementation Reference

  • The handler function for the 'create_event' MCP tool. It extracts parameters, calls the API client to create the event, formats the response using formatEvent, and returns MCP-formatted content or error.
    async ({ title, description, start_time, end_time, location, capacity }) => {
      try {
        const apiClient = getClient();
        const event = await apiClient.createEvent({
          title,
          description,
          start_time,
          end_time,
          location,
          capacity
        });
        return {
          content: [{ type: 'text', text: `Event created successfully!\n\n${formatEvent(event)}` }]
        };
      } catch (error) {
        return {
          content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the 'create_event' MCP tool.
    {
      title: z.string().describe('Title of the event'),
      description: z.string().describe('Description of the event'),
      start_time: z.string().describe('Start time in ISO 8601 format (e.g., 2024-12-25T10:00:00Z)'),
      end_time: z.string().describe('End time in ISO 8601 format (e.g., 2024-12-25T18:00:00Z)'),
      location: z.string().describe('Location of the event'),
      capacity: z.number().describe('Maximum number of attendees')
    },
  • src/index.ts:108-140 (registration)
    Complete registration of the 'create_event' MCP tool using server.tool, including name, description, schema, and inline handler.
    server.tool(
      'create_event',
      'Create a new event. Requires title, description, start/end times, location, and capacity.',
      {
        title: z.string().describe('Title of the event'),
        description: z.string().describe('Description of the event'),
        start_time: z.string().describe('Start time in ISO 8601 format (e.g., 2024-12-25T10:00:00Z)'),
        end_time: z.string().describe('End time in ISO 8601 format (e.g., 2024-12-25T18:00:00Z)'),
        location: z.string().describe('Location of the event'),
        capacity: z.number().describe('Maximum number of attendees')
      },
      async ({ title, description, start_time, end_time, location, capacity }) => {
        try {
          const apiClient = getClient();
          const event = await apiClient.createEvent({
            title,
            description,
            start_time,
            end_time,
            location,
            capacity
          });
          return {
            content: [{ type: 'text', text: `Event created successfully!\n\n${formatEvent(event)}` }]
          };
        } catch (error) {
          return {
            content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
            isError: true
          };
        }
      }
    );
  • API client method called by the MCP handler to perform the actual HTTP POST to create the event.
    async createEvent(eventData: EventCreateRequest): Promise<Event> {
      try {
        const response: AxiosResponse<Event> = await this.client.post('/api/events/', eventData);
        return response.data;
      } catch (error) {
        throw new Error(`Failed to create event: ${getErrorMessage(error)}`);
      }
    }
  • TypeScript interface for the event creation request data structure used by the API client.
    export interface EventCreateRequest {
      title: string;
      description: string;
      start_time: string;
      end_time: string;
      location: string;
      capacity: number;
      registration_schema?: Record<string, unknown>[];
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Create a new event' which implies a write/mutation operation, but doesn't address permissions needed, whether creation is idempotent, what happens on duplicate titles, or what the response contains. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 concise - one sentence that states the purpose and lists required parameters. It's front-loaded with the core action. While efficient, it could potentially benefit from slightly more context given the mutation nature of the operation.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address what happens after creation (success response, error conditions), permissions needed, or how this tool relates to sibling operations like 'update_event' or 'delete_event'. The agent lacks critical context for proper tool invocation.

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 all 6 parameters. The description lists the required parameters but adds no additional semantic context beyond what's in the schema (e.g., format expectations beyond ISO 8601 for times, what 'capacity' means operationally). Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Create a new event') and specifies the required resources (title, description, times, location, capacity). It distinguishes from siblings like 'update_event' by focusing on creation, but doesn't explicitly differentiate from other creation-related tools that might exist in the broader context.

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 like 'update_event' or 'list_events'. It mentions required parameters but doesn't indicate prerequisites, constraints, or appropriate contexts for event creation versus other operations.

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