Skip to main content
Glama
NotoriousArnav

EventHorizon MCP Server

get_event

Retrieve detailed information about a specific event using its unique ID to access event data from the EventHorizon platform.

Instructions

Get detailed information about a specific event by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesThe ID of the event to retrieve

Implementation Reference

  • The async handler function that executes the 'get_event' tool: fetches the event using apiClient.getEvent, formats it, and returns the response or error.
    async ({ event_id }) => {
      try {
        const apiClient = getClient();
        const event = await apiClient.getEvent(event_id);
        return {
          content: [{ type: 'text', text: formatEvent(event) }]
        };
      } catch (error) {
        return {
          content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
          isError: true
        };
      }
    }
  • Zod input schema defining the 'event_id' parameter for the 'get_event' tool.
    {
      event_id: z.number().describe('The ID of the event to retrieve')
    },
  • src/index.ts:86-106 (registration)
    Registration of the 'get_event' tool on the MCP server using server.tool().
    server.tool(
      'get_event',
      'Get detailed information about a specific event by its ID.',
      {
        event_id: z.number().describe('The ID of the event to retrieve')
      },
      async ({ event_id }) => {
        try {
          const apiClient = getClient();
          const event = await apiClient.getEvent(event_id);
          return {
            content: [{ type: 'text', text: formatEvent(event) }]
          };
        } catch (error) {
          return {
            content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
            isError: true
          };
        }
      }
    );
  • Helper function used by the handler to format the event data into a readable string.
    function formatEvent(event: Event): string {
      return `Event: ${event.title} (ID: ${event.id})
      Description: ${event.description}
      Location: ${event.location}
      Start: ${event.start_time}
      End: ${event.end_time}
      Capacity: ${event.capacity}
      Organizer: ${event.organizer.username}
      Registered: ${event.is_registered ? 'Yes' : 'No'}`;
    }
  • API client method called by the tool handler to fetch event details via HTTP GET request.
    async getEvent(eventId: number): Promise<Event> {
      try {
        const response: AxiosResponse<Event> = await this.client.get(`/api/events/${eventId}/`);
        return response.data;
      } catch (error) {
        throw new Error(`Failed to get 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 states the tool retrieves 'detailed information' but doesn't specify what that includes (e.g., event name, date, location), whether it's read-only, requires authentication, or has rate limits. For a tool with zero annotation coverage, this is a significant gap in behavioral context.

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 a single, efficient sentence that front-loads the core purpose ('Get detailed information about a specific event by its ID'). There is no wasted text, making it highly concise and well-structured for quick comprehension.

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?

Given the lack of annotations and output schema, the description is incomplete for a tool that retrieves 'detailed information'. It doesn't explain what details are returned (e.g., event attributes), potential errors (e.g., invalid ID), or how it differs from siblings like 'list_events'. This leaves gaps in understanding the tool's full context and behavior.

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?

The schema description coverage is 100%, with the single parameter 'event_id' clearly documented as 'The ID of the event to retrieve'. The description adds no additional meaning beyond this, such as format examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 ('Get detailed information') and resource ('specific event by its ID'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this from sibling tools like 'list_events' (which retrieves multiple events) or 'get_event_registrations' (which focuses on registrations rather than event details), missing full sibling differentiation.

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 that 'list_events' is for multiple events or 'get_event_registrations' is for registration data, nor does it specify prerequisites like needing a valid event ID. This leaves the agent with minimal context for tool selection.

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