Skip to main content
Glama

login_help

Resolve login issues and access troubleshooting guidance for the N Lobby school portal. Provide your email for personalized assistance.

Instructions

Get help and troubleshooting tips for N Lobby login

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoYour email address (optional, for personalized help)

Implementation Reference

  • The main execution logic for the 'login_help' tool. Parses optional email argument, validates it using CredentialManager, constructs a comprehensive help message with user-type specific guidance, troubleshooting tips, and session statistics, then returns it as text content.
    case "login_help": {
      const { email } = args as { email?: string };
    
      let helpMessage = `[LOGIN] N Lobby Login Help\n\n`;
    
      if (email) {
        const emailValidation =
          this.credentialManager.validateEmail(email);
        helpMessage += `[EMAIL] Email: ${email}\n`;
        helpMessage += `[USER] User Type: ${emailValidation.userType}\n`;
        helpMessage += `[SUCCESS] Valid: ${emailValidation.valid ? "Yes" : "No"}\n\n`;
    
        if (!emailValidation.valid) {
          helpMessage += `[ERROR] Issue: ${emailValidation.message}\n\n`;
        }
    
        helpMessage += this.credentialManager.getLoginGuidance(
          emailValidation.userType,
        );
      } else {
        helpMessage += this.credentialManager.getLoginGuidance("unknown");
      }
    
      helpMessage += `\n\n${this.credentialManager.getTroubleshootingTips()}`;
    
      // Add session stats
      const stats = this.credentialManager.getSessionStats();
      helpMessage += `\n\n[STATUS] Session Stats:\n- Active sessions: ${stats.total - stats.expired}\n- Expired sessions: ${stats.expired}`;
    
      return {
        content: [
          {
            type: "text",
            text: helpMessage,
          },
        ],
      };
    }
  • src/server.ts:418-431 (registration)
    Registers the 'login_help' tool in the MCP server's tool list, including its name, description, and input schema defining an optional 'email' parameter.
    {
      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)",
          },
        },
      },
    },
  • Defines the input schema for the 'login_help' tool, specifying an optional string 'email' parameter.
      inputSchema: {
        type: "object",
        properties: {
          email: {
            type: "string",
            description:
              "Your email address (optional, for personalized help)",
          },
        },
      },
    },
  • Helper method called by login_help handler to validate the provided email and determine user type (student, staff, parent, or unknown) based on domain.
    validateEmail(email: string): {
      valid: boolean;
      userType: "student" | "staff" | "parent" | "unknown";
      message?: string;
    } {
      const emailRegex = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
    
      if (!emailRegex.test(email)) {
        return {
          valid: false,
          userType: "unknown",
          message: "Invalid email format",
        };
      }
    
      const domain = email.split("@")[1].toLowerCase();
    
      // N High School Group domains
      if (domain === "nnn.ed.jp") {
        return { valid: true, userType: "student" };
      } else if (domain === "nnn.ac.jp") {
        return { valid: true, userType: "staff" };
      } else if (
        domain === "gmail.com" ||
        domain === "yahoo.com" ||
        domain === "outlook.com" ||
        domain === "hotmail.com"
      ) {
        return { valid: true, userType: "parent" };
      } else {
        return { valid: true, userType: "parent" }; // Allow other domains for parents
      }
    }
  • Helper method providing user-type specific login instructions, used by the login_help handler to generate personalized guidance.
      getLoginGuidance(
        userType: "student" | "staff" | "parent" | "unknown",
      ): string {
        switch (userType) {
          case "student":
            return `
    [STUDENT] Student Login Guide:
    - Use your @nnn.ed.jp email address
    - Use your N High School password
    - If you have 2FA enabled, you'll need to complete it during login
    - Contact your homeroom teacher if you've forgotten your password`;
    
          case "staff":
            return `
    [STAFF] Staff Login Guide:
    - Use your @nnn.ac.jp email address
    - Use your N High School staff password
    - If you have 2FA enabled, you'll need to complete it during login
    - Contact IT support if you're having trouble accessing your account`;
    
          case "parent":
            return `
    [PARENT] Parent Login Guide:
    - Use the email address registered with your child's school account
    - Use the password you set when creating your parent account
    - If you haven't created a parent account yet, contact your child's school
    - If you've forgotten your password, use the password reset option`;
    
          default:
            return `
    [LOGIN] General Login Guide:
    - Use your registered email address
    - Use your N Lobby password
    - If you have 2FA enabled, you'll need to complete it during login
    - Contact support if you're having trouble`;
        }
      }
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. While 'Get help and troubleshooting tips' suggests a read-only, informational operation, it doesn't clarify what form the help takes (text, links, step-by-step guidance), whether it requires authentication, if it has rate limits, or what happens when the optional email parameter is provided. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 any unnecessary words. It's appropriately sized for a simple help tool and front-loads the essential information. Every word earns its place.

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?

For a simple informational tool with one optional parameter and no output schema, the description is minimally adequate. However, given the lack of annotations and the presence of multiple sibling tools addressing similar login concerns, the description should do more to clarify this tool's specific role and what kind of help it provides versus alternatives.

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 description provides no parameter information, but the input schema has 100% description coverage with a single optional 'email' parameter clearly documented as 'Your email address (optional, for personalized help)'. With high schema coverage and only one parameter, the baseline score of 3 is appropriate - the schema does the heavy lifting, and the description doesn't add value beyond what's already in the structured data.

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 tool's purpose as 'Get help and troubleshooting tips for N Lobby login' - a specific verb ('Get help and troubleshooting tips') applied to a specific resource ('N Lobby login'). However, it doesn't distinguish this tool from potential alternatives like 'debug_connection' or 'verify_authentication' among the sibling tools, which might also address login issues.

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. With sibling tools like 'debug_connection', 'verify_authentication', and 'interactive_login' that might address similar login-related concerns, there's no indication of when this help-focused tool is preferable versus when those diagnostic or action-oriented tools should be used instead.

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