Skip to main content
Glama

test_calendar_endpoints

Test personal and school calendar endpoints by specifying date ranges to verify functionality and retrieve schedule data.

Instructions

Test both personal and school calendar endpoints

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_dateNoStart date in YYYY-MM-DD format (optional). If only from_date is provided, it will be treated as a single day.
to_dateNoEnd date in YYYY-MM-DD format (optional). Must be at least 1 day after from_date when both are provided.

Implementation Reference

  • Main execution logic for the test_calendar_endpoints tool: parses date parameters, constructs date range, invokes API test method, generates formatted test report showing personal and school calendar endpoint status, event counts, and summary statistics.
    case "test_calendar_endpoints":
      try {
        const { from_date, to_date } = args as {
          from_date?: string;
          to_date?: string;
        };
    
        // Create date range if provided
        let dateRange;
        if (from_date && to_date) {
          dateRange = this.api.createDateRange(from_date, to_date);
        } else if (from_date) {
          // Single day range
          dateRange = this.api.createSingleDayRange(from_date);
        }
    
        const testResults =
          await this.api.testCalendarEndpoints(dateRange);
    
        const reportLines = [
          "[TEST] Calendar Endpoints Test Results",
          "=".repeat(40),
          "",
          `[DATE] Test Period: ${
            dateRange
              ? `${dateRange.from.toDateString()} to ${dateRange.to.toDateString()}`
              : "Current week (default)"
          }`,
          "",
          "[PERSONAL] Personal Calendar:",
          `   Status: ${testResults.personal.success ? "[SUCCESS] Success" : "[ERROR] Failed"}`,
          `   Events: ${testResults.personal.count}`,
          testResults.personal.error
            ? `   Error: ${testResults.personal.error}`
            : "",
          "",
          "[SCHOOL] School Calendar:",
          `   Status: ${testResults.school.success ? "[SUCCESS] Success" : "[ERROR] Failed"}`,
          `   Events: ${testResults.school.count}`,
          testResults.school.error
            ? `   Error: ${testResults.school.error}`
            : "",
          "",
          "[STATUS] Summary:",
          `   Total Endpoints: 2`,
          `   Successful: ${
            (testResults.personal.success ? 1 : 0) +
            (testResults.school.success ? 1 : 0)
          }`,
          `   Failed: ${
            (testResults.personal.success ? 0 : 1) +
            (testResults.school.success ? 0 : 1)
          }`,
          `   Total Events: ${testResults.personal.count + testResults.school.count}`,
        ];
    
        return {
          content: [
            {
              type: "text",
              text: reportLines.filter(Boolean).join("\n"),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error testing calendar endpoints: ${
                error instanceof Error ? error.message : "Unknown error"
              }\n\nTo authenticate:\n1. Login to N Lobby in your browser\n2. Open Developer Tools (F12)\n3. Go to Application/Storage tab\n4. Copy cookies and use the set_cookies tool\n5. Use health_check to verify connection`,
            },
          ],
        };
      }
  • Input schema definition for the test_calendar_endpoints tool, specifying optional from_date and to_date parameters with descriptions matching other calendar tools.
    {
      name: "test_calendar_endpoints",
      description: "Test both personal and school calendar endpoints",
      inputSchema: {
        type: "object",
        properties: {
          from_date: {
            type: "string",
            description:
              "Start date in YYYY-MM-DD format (optional). If only from_date is provided, it will be treated as a single day.",
          },
          to_date: {
            type: "string",
            description:
              "End date in YYYY-MM-DD format (optional). Must be at least 1 day after from_date when both are provided.",
          },
        },
      },
    },
  • src/server.ts:154-450 (registration)
    Tool registration within the MCP ListToolsRequestSchema handler, where test_calendar_endpoints is included in the list of available tools returned to clients.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "get_news",
            description: "Retrieve school news",
            inputSchema: {
              type: "object",
              properties: {
                category: {
                  type: "string",
                  description: "Filter by category (optional)",
                },
                limit: {
                  type: "number",
                  description:
                    "Maximum number of news items to retrieve (optional, default: 10)",
                  minimum: 1,
                  default: 10,
                },
                sort: {
                  type: "string",
                  description:
                    "Sort order: 'newest' (default), 'oldest', 'title-asc', 'title-desc'",
                  enum: ["newest", "oldest", "title-asc", "title-desc"],
                },
              },
            },
          },
          {
            name: "get_news_detail",
            description:
              "Retrieve detailed information for a specific news article",
            inputSchema: {
              type: "object",
              properties: {
                newsId: {
                  type: "string",
                  description: "The ID of the news article to retrieve",
                },
                markAsRead: {
                  type: "boolean",
                  description:
                    "Mark the news article as read (optional, default: false)",
                  default: false,
                },
              },
              required: ["newsId"],
            },
          },
          {
            name: "get_account_info",
            description:
              "Extract account information by parsing Next.js flight data from a rendered page",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
          {
            name: "get_student_card_screenshot",
            description:
              "Capture a screenshot of the student ID card by following the secure portal redirect flow",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
          {
            name: "get_required_courses",
            description:
              "Retrieve required courses information with detailed progress tracking",
            inputSchema: {
              type: "object",
              properties: {
                grade: {
                  type: "number",
                  description: "Filter by grade level (1, 2, or 3) (optional)",
                },
                semester: {
                  type: "string",
                  description:
                    'Filter by term year (e.g., "2024", "2025") (optional)',
                },
                category: {
                  type: "string",
                  description:
                    'Filter by curriculum category (e.g., "国語", "数学", "英語") (optional)',
                },
              },
            },
          },
          {
            name: "get_schedule",
            description:
              "Get school schedule for a specific date (backward compatibility)",
            inputSchema: {
              type: "object",
              properties: {
                date: {
                  type: "string",
                  description:
                    "Date in YYYY-MM-DD format (optional, defaults to today)",
                },
              },
            },
          },
          {
            name: "get_calendar_events",
            description: "Get calendar events with advanced options",
            inputSchema: {
              type: "object",
              properties: {
                calendar_type: {
                  type: "string",
                  enum: ["personal", "school"],
                  description:
                    "Type of calendar to retrieve (personal or school)",
                  default: "personal",
                },
                from_date: {
                  type: "string",
                  description:
                    "Start date in YYYY-MM-DD format (optional). If only from_date is provided, it will be treated as a single day.",
                },
                to_date: {
                  type: "string",
                  description:
                    "End date in YYYY-MM-DD format (optional). Must be at least 1 day after from_date when both are provided.",
                },
                period: {
                  type: "string",
                  enum: ["today", "week", "month"],
                  description:
                    'Predefined period (optional, overrides from/to dates). Use "today" for single day queries.',
                },
              },
            },
          },
          {
            name: "test_calendar_endpoints",
            description: "Test both personal and school calendar endpoints",
            inputSchema: {
              type: "object",
              properties: {
                from_date: {
                  type: "string",
                  description:
                    "Start date in YYYY-MM-DD format (optional). If only from_date is provided, it will be treated as a single day.",
                },
                to_date: {
                  type: "string",
                  description:
                    "End date in YYYY-MM-DD format (optional). Must be at least 1 day after from_date when both are provided.",
                },
              },
            },
          },
    
          {
            name: "set_cookies",
            description: "Set authentication cookies for N Lobby access",
            inputSchema: {
              type: "object",
              properties: {
                cookies: {
                  type: "string",
                  description:
                    "Cookie string from authenticated N Lobby session",
                },
              },
              required: ["cookies"],
            },
          },
          {
            name: "check_cookies",
            description: "Check if authentication cookies are set",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
          {
            name: "health_check",
            description: "Check if N Lobby API connection is working",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
    
          {
            name: "debug_connection",
            description: "Debug N Lobby connection with detailed information",
            inputSchema: {
              type: "object",
              properties: {
                endpoint: {
                  type: "string",
                  description: "Endpoint to test (default: /news)",
                  default: "/news",
                },
              },
            },
          },
    
          {
            name: "test_page_content",
            description: "Test page content retrieval and show sample content",
            inputSchema: {
              type: "object",
              properties: {
                endpoint: {
                  type: "string",
                  description: "Endpoint to test (default: /news)",
                  default: "/news",
                },
                length: {
                  type: "number",
                  description: "Number of characters to show (default: 1000)",
                  default: 1000,
                },
              },
            },
          },
    
          {
            name: "test_trpc_endpoint",
            description: "Test specific tRPC endpoint with detailed response",
            inputSchema: {
              type: "object",
              properties: {
                method: {
                  type: "string",
                  description:
                    "tRPC method to test (e.g., news.getUnreadNewsCount, user.updateLastAccess)",
                  default: "user.updateLastAccess",
                },
                params: {
                  type: "string",
                  description: "JSON string of parameters (optional)",
                },
              },
            },
          },
          {
            name: "verify_authentication",
            description:
              "Verify authentication status and cookie synchronization across all clients",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
    
          {
            name: "interactive_login",
            description:
              "Open browser for manual login to N Lobby (no credentials required)",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
          {
            name: "login_help",
            description: "Get help and troubleshooting tips for N Lobby login",
            inputSchema: {
              type: "object",
              properties: {
                email: {
                  type: "string",
                  description:
                    "Your email address (optional, for personalized help)",
                },
              },
            },
          },
          {
            name: "mark_news_as_read",
            description: "Mark news articles as read",
            inputSchema: {
              type: "object",
              properties: {
                ids: {
                  type: "array",
                  items: {
                    type: "string",
                  },
                  description: "Array of news article IDs to mark as read",
                },
              },
              required: ["ids"],
            },
          },
        ],
      };
Behavior2/5

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

With no annotations, the description carries full burden but only states it tests endpoints without disclosing behavioral traits. It doesn't explain what 'test' entails (e.g., side effects, output format, error handling), making it insufficient for a tool with potential operational impacts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 scope (personal and school calendars). It's appropriately sized and front-loaded, with no wasted words, though it could be more informative.

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 complexity of a testing tool with no annotations and no output schema, the description is incomplete. It lacks details on what testing involves, expected results, or how it integrates with the system, failing to compensate for missing structured data.

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 fully documents the two optional date parameters. The description adds no meaning beyond the schema, as it doesn't mention parameters or their role in testing. Baseline 3 is appropriate since the schema handles parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool tests calendar endpoints, which is a clear purpose, but it's vague about what 'test' means (e.g., validation, performance, functionality). It distinguishes from siblings like 'get_calendar_events' by implying testing rather than data retrieval, but lacks specificity on the verb's action.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), context for testing, or compare to siblings like 'debug_connection' or 'test_page_content', leaving usage ambiguous.

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/minagishl/nlobby-cli'

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