Skip to main content
Glama
NotoriousArnav

EventHorizon MCP Server

get_my_profile

Retrieve your user profile details from the EventHorizon platform to access personal information and manage your account settings.

Instructions

Get the current user's profile information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration and inline handler for 'get_my_profile'. Fetches the current user's profile using EventHorizonClient and formats it as a text response.
    server.tool(
      'get_my_profile',
      'Get the current user\'s profile information.',
      {},
      async () => {
        try {
          const apiClient = getClient();
          const profile = await apiClient.getCurrentProfile();
          return {
            content: [{
              type: 'text',
              text: `User Profile:
      Username: ${profile.username}
      Email: ${profile.email}
      Name: ${profile.first_name} ${profile.last_name}
      Bio: ${profile.profile.bio || 'Not set'}
      Location: ${profile.profile.location || 'Not set'}
      Phone: ${profile.profile.phone_number || 'Not set'}
      Joined: ${profile.date_joined}`
            }]
          };
        } catch (error) {
          return {
            content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
            isError: true
          };
        }
      }
    );
  • EventHorizonClient method that performs the actual API call to retrieve the current user's profile from '/accounts/api/me/'.
    async getCurrentProfile(): Promise<User & { profile: Profile }> {
      try {
        const response: AxiosResponse<User & { profile: Profile }> = await this.client.get('/accounts/api/me/');
        return response.data;
      } catch (error) {
        throw new Error(`Failed to get user profile: ${getErrorMessage(error)}`);
      }
    }
  • TypeScript interfaces defining the structure of User and Profile data used by the get_my_profile tool.
    export interface User {
      id: number;
      username: string;
      email: string;
      first_name: string;
      last_name: string;
      date_joined: string;
    }
    
    export interface Profile {
      bio: string;
      location: string;
      phone_number: string;
      avatar: string;
      social_links: SocialLink[];
    }
    
    export interface SocialLink {
      platform: 'github' | 'twitter' | 'linkedin' | 'instagram' | 'facebook' | 'website' | 'other';
      url: string;
    }
  • Lazy-initializes and returns the EventHorizonClient instance used by all tools, including get_my_profile.
    function getClient(): EventHorizonClient {
      if (!client) {
        const errors = validateConfig();
        if (errors.length > 0) {
          throw new Error(`Configuration errors: ${errors.join('; ')}`);
        }
        client = new EventHorizonClient();
      }
      return client;
    }
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 profile information but doesn't specify what data is included (e.g., name, email, preferences), whether it requires authentication, or how errors are handled. For a read operation with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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, clear sentence that directly states the tool's function without any unnecessary words. It's front-loaded with the core purpose and efficiently communicates the essential information. Every part of the description earns its place, making it highly concise and well-structured.

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 simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate. It explains what the tool does but lacks details on returned data format or behavioral context. For a read-only profile tool, more information about output structure would be helpful, but the absence of an output schema means the description doesn't fully compensate.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose. This aligns with the baseline expectation for tools without parameters, though it doesn't add extra semantic value beyond the schema.

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') and resource ('current user's profile information'), making the purpose immediately understandable. It distinguishes this tool from siblings like get_event or get_my_registrations by focusing specifically on profile data. However, it doesn't explicitly differentiate from potential similar tools (though none are present in the sibling list), preventing 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 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. While the sibling list includes tools for events and registrations, there's no explicit comparison or context for choosing this tool. It lacks any mention of prerequisites, timing, or relationship to other tools, leaving usage entirely implicit.

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