Skip to main content
Glama
tHeMaskedMan981

Network School Events MCP Server

search_events

Search Network School calendar events by name or description to find relevant activities and opportunities.

Instructions

Search Network School events by name or description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string

Implementation Reference

  • Handler for the 'search_events' tool: validates query input, fetches events, filters using searchEvents helper, formats output with formatEventsList, and returns text content.
    case 'search_events': {
      const query = args?.query as string;
      
      if (!query || typeof query !== 'string') {
        return {
          content: [
            {
              type: 'text',
              text: 'Error: query parameter is required and must be a string',
            },
          ],
          isError: true,
        };
      }
    
      const response = await lumaClient.fetchEvents();
      const matchingEvents = searchEvents(response.entries, query);
      const formatted = formatEventsList(
        matchingEvents,
        `No events found matching "${query}".`
      );
    
      return {
        content: [
          {
            type: 'text',
            text: formatted,
          },
        ],
      };
    }
  • src/index.ts:67-80 (registration)
    Registration of the 'search_events' tool in list_tools handler, including name, description, and input schema.
    {
      name: 'search_events',
      description: 'Search Network School events by name or description',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search query string',
          },
        },
        required: ['query'],
      },
    },
  • Input schema definition for 'search_events' tool: requires 'query' string.
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Search query string',
        },
      },
      required: ['query'],
    },
  • Helper function searchEvents that filters events by matching query in event name or description (case-insensitive).
    export function searchEvents(entries: LumaEntry[], query: string): LumaEntry[] {
      const lowerQuery = query.toLowerCase();
      
      return entries.filter(entry => {
        const nameMatch = entry.event.name.toLowerCase().includes(lowerQuery);
        const descriptionMatch = entry.event.description?.toLowerCase().includes(lowerQuery) || false;
        return nameMatch || descriptionMatch;
      });
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the search functionality without mentioning whether this is a read-only operation, what permissions are needed, how results are returned (pagination, format), or any rate limits. For a search tool with zero annotation coverage, this leaves significant behavioral gaps.

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 with zero wasted words. It's appropriately sized for a simple search tool and front-loads the essential information (search functionality and target resource).

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?

For a search tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the search returns (event objects, IDs, summaries), how results are structured, or any limitations (e.g., partial matches, case sensitivity). Given the lack of structured data elsewhere, the description should provide more context about the tool's behavior and output.

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%, so the schema already documents the single 'query' parameter. The description adds marginal value by specifying it searches 'by name or description', but doesn't provide additional syntax, format, or search behavior details beyond what the schema indicates. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('search') and resource ('Network School events'), and specifies the searchable fields ('by name or description'). However, it doesn't explicitly differentiate from sibling tools like 'search_wiki' which searches a different resource, or 'get_todays_events'/'get_upcoming_events' which retrieve events without search functionality.

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 'get_upcoming_events'. It doesn't indicate whether this is for broad searches versus filtered retrieval, or mention any prerequisites or exclusions for usage.

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