Skip to main content
Glama
tHeMaskedMan981

Network School Events MCP Server

get_upcoming_events

Retrieve upcoming Network School calendar events for the next specified days to help users plan and stay informed about available activities.

Instructions

Get Network School events happening in the next N days

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days to look ahead (default: 7)

Implementation Reference

  • Handler logic for 'get_upcoming_events' tool: validates input days, fetches events via LumaClient, filters upcoming events using filterUpcomingEvents, formats the list, and returns formatted text response.
    case 'get_upcoming_events': {
      const days = (args?.days as number) || 7;
      
      if (typeof days !== 'number' || days < 1) {
        return {
          content: [
            {
              type: 'text',
              text: 'Error: days parameter must be a positive number',
            },
          ],
          isError: true,
        };
      }
    
      const response = await lumaClient.fetchEvents();
      const upcomingEvents = filterUpcomingEvents(response.entries, days);
      const formatted = formatEventsList(
        upcomingEvents,
        `No events scheduled in the next ${days} day${days !== 1 ? 's' : ''}.`
      );
    
      return {
        content: [
          {
            type: 'text',
            text: formatted,
          },
        ],
      };
    }
  • src/index.ts:53-66 (registration)
    Registration of the 'get_upcoming_events' tool in the list_tools handler, including name, description, and input schema definition.
    {
      name: 'get_upcoming_events',
      description: 'Get Network School events happening in the next N days',
      inputSchema: {
        type: 'object',
        properties: {
          days: {
            type: 'number',
            description: 'Number of days to look ahead (default: 7)',
            default: 7,
          },
        },
      },
    },
  • Input schema definition for the 'get_upcoming_events' tool, specifying the 'days' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        days: {
          type: 'number',
          description: 'Number of days to look ahead (default: 7)',
          default: 7,
        },
      },
    },
  • Helper function filterUpcomingEvents that filters Luma events starting within the next N days, used in the tool handler.
    export function filterUpcomingEvents(entries: LumaEntry[], days: number): LumaEntry[] {
      const now = new Date();
      const futureDate = addDays(now, days);
      
      return entries.filter(entry => {
        const startDate = parseISO(entry.event.start_at);
        return isWithinInterval(startDate, {
          start: startOfDay(now),
          end: endOfDay(futureDate)
        });
      });
    }
  • Helper function formatEventsList that formats a list of events into a readable string, used in the tool handler.
    export function formatEventsList(entries: LumaEntry[], emptyMessage: string = 'No events found.'): string {
      if (entries.length === 0) {
        return emptyMessage;
      }
      
      return entries.map(entry => formatEvent(entry)).join('\n\n');
    }
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 retrieving events but doesn't cover aspects like permissions needed, rate limits, pagination, or response format. This leaves significant gaps for a tool that likely queries data.

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 directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, earning a high score for conciseness.

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 simple input schema (1 parameter with full coverage) and no output schema or annotations, the description is adequate but incomplete. It covers the basic purpose but lacks details on behavior, usage context, or output, making it minimally viable with clear gaps.

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 input schema has 100% description coverage, fully documenting the 'days' parameter with its type, description, and default. The description adds no additional parameter details beyond what the schema provides, so it meets the baseline of 3.

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 ('Network School events happening in the next N days'), making the purpose understandable. It doesn't explicitly differentiate from sibling tools like get_todays_events or search_events, which limits it to a 4 rather than a 5.

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 get_todays_events or search_events. It implies usage for upcoming events but lacks explicit when/when-not instructions or prerequisites, resulting in a minimal score.

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/tHeMaskedMan981/ns-mcp'

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