Skip to main content
Glama
NotoriousArnav

EventHorizon MCP Server

manage_registration

Approve, waitlist, or cancel event registrations as an organizer to control attendee participation.

Instructions

Manage a registration (approve, waitlist, or cancel). Only available to the event organizer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
registration_idYesThe ID of the registration to manage
actionYesAction to take on the registration

Implementation Reference

  • The asynchronous handler function for the 'manage_registration' MCP tool. It retrieves the API client, calls manageRegistration on it, formats the response using formatRegistration, and returns success or error content.
    async ({ registration_id, action }) => {
      try {
        const apiClient = getClient();
        const registration = await apiClient.manageRegistration(registration_id, action);
        return {
          content: [{ type: 'text', text: `Registration ${action}d successfully!\n\n${formatRegistration(registration)}` }]
        };
      } catch (error) {
        return {
          content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
          isError: true
        };
      }
    }
  • Zod input schema for the 'manage_registration' tool defining parameters: registration_id (number) and action (one of 'approve', 'waitlist', 'cancel').
    {
      registration_id: z.number().describe('The ID of the registration to manage'),
      action: z.enum(['approve', 'waitlist', 'cancel']).describe('Action to take on the registration')
    },
  • src/index.ts:279-300 (registration)
    MCP server.tool registration for the 'manage_registration' tool, specifying name, description, input schema, and handler function.
    server.tool(
      'manage_registration',
      'Manage a registration (approve, waitlist, or cancel). Only available to the event organizer.',
      {
        registration_id: z.number().describe('The ID of the registration to manage'),
        action: z.enum(['approve', 'waitlist', 'cancel']).describe('Action to take on the registration')
      },
      async ({ registration_id, action }) => {
        try {
          const apiClient = getClient();
          const registration = await apiClient.manageRegistration(registration_id, action);
          return {
            content: [{ type: 'text', text: `Registration ${action}d successfully!\n\n${formatRegistration(registration)}` }]
          };
        } catch (error) {
          return {
            content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
            isError: true
          };
        }
      }
    );
  • Utility function to format Registration data into a readable string for tool responses.
    function formatRegistration(reg: Registration): string {
      const eventInfo = typeof reg.event === 'object' ? reg.event.title : `Event ID: ${reg.event}`;
      const userInfo = typeof reg.user === 'object' ? reg.user.username : `User ID: ${reg.user}`;
      return `Registration (ID: ${reg.id})
      Event: ${eventInfo}
      User: ${userInfo}
      Status: ${reg.status}
      Registered at: ${reg.registered_at}`;
    }
  • EventHorizonClient method that sends POST request to manage a specific registration via the backend API.
    async manageRegistration(registrationId: number, action: 'approve' | 'waitlist' | 'cancel'): Promise<Registration> {
      try {
        const response: AxiosResponse<Registration> = await this.client.post(`/api/registrations/${registrationId}/manage/`, { action });
        return response.data;
      } catch (error) {
        throw new Error(`Failed to manage registration ${registrationId}: ${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 permission requirement ('Only available to the event organizer') but lacks details on side effects (e.g., whether actions are reversible, notifications sent, or impact on event capacity), rate limits, or error conditions. For a mutation tool with zero annotation coverage, this is insufficient.

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 sentences, front-loaded with the core purpose and followed by a critical constraint. Every word earns its place, with no redundancy or fluff, making it highly efficient and easy to parse.

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 (mutation with permissions) and lack of annotations or output schema, the description is minimally adequate. It covers purpose and permissions but misses behavioral details like side effects or return values. For a tool with no structured safety hints, it should do more to compensate.

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%, with clear descriptions for both parameters (registration_id and action with enum values). The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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

Purpose5/5

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

The description clearly states the verb ('manage') and resource ('registration'), specifying the exact actions (approve, waitlist, or cancel). It distinguishes from siblings like 'register_for_event' (create) and 'unregister_from_event' (delete) by focusing on status management rather than creation or deletion.

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 explicitly states 'Only available to the event organizer,' providing clear context about user permissions. However, it does not specify when to use this tool versus alternatives like 'update_event' for broader event changes or 'unregister_from_event' for cancellation by attendees, leaving some ambiguity in sibling differentiation.

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