Skip to main content
Glama
tHeMaskedMan981

Network School Events MCP Server

get_todays_events

Retrieve all Network School calendar events scheduled for today to stay informed about daily activities and opportunities.

Instructions

Get all Network School events happening today

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:45-52 (registration)
    Registration of the 'get_todays_events' tool in the list_tools handler, including name, description, and input schema.
    {
      name: 'get_todays_events',
      description: 'Get all Network School events happening today',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for get_todays_events tool: empty object (no parameters).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • Core handler logic: fetches all events via LumaClient, filters for today using filterTodaysEvents, formats with formatEventsList, returns formatted text response.
    case 'get_todays_events': {
      const response = await lumaClient.fetchEvents();
      const todaysEvents = filterTodaysEvents(response.entries);
      const formatted = formatEventsList(
        todaysEvents,
        'No events scheduled for today.'
      );
    
      return {
        content: [
          {
            type: 'text',
            text: formatted,
          },
        ],
      };
    }
  • Helper function to filter events occurring today using date-fns isToday check.
    export function filterTodaysEvents(entries: LumaEntry[]): LumaEntry[] {
      return entries.filter(entry => {
        const startDate = parseISO(entry.event.start_at);
        return isToday(startDate);
      });
    }
  • Helper function to format a list of events into a readable markdown bullet-point list, or return empty message.
    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?

No annotations are provided, so the description carries full burden for behavioral disclosure. It states it 'gets' events, implying a read-only operation, but doesn't specify whether this requires authentication, how results are returned (e.g., format, pagination), or any rate limits. This leaves significant gaps for a tool with zero annotation coverage.

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 without any wasted words. It's appropriately sized for a simple tool with no parameters, making it easy for an agent to parse quickly.

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. It doesn't explain what 'events' entail (e.g., structure, fields), how results are returned, or any behavioral constraints. For a tool that presumably returns data, more context is needed to guide the agent effectively.

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 tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter explanation in the description. The description appropriately doesn't mention parameters, earning a baseline score of 4 for not adding unnecessary information.

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 today'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_upcoming_events' or 'search_events', which prevents a perfect score, but the temporal scope 'today' provides some implicit distinction.

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_upcoming_events' or 'search_events'. It implies usage for today's events only, but doesn't specify exclusions or prerequisites, leaving the agent to infer context without explicit direction.

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