Skip to main content
Glama
nieperdragon

MCP Login Server

by nieperdragon

navigate_to_pim

Access the Personal Information Management page directly from the left-hand navigation menu after logging in.

Instructions

Navigates to the PIM (Personal Information Management) page using the left-hand navigation menu. Assumes user is already logged in.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'navigate_to_pim' tool. It generates and returns a detailed text response with navigation steps to the PIM page, assuming the user is logged in. Includes error handling.
        async () => {
          try {
            const navigationSteps = [
              "Locate the left-hand navigation menu",
              "Find the 'PIM' menu item in the navigation list",
              "Click on the 'PIM' link to navigate to the PIM module",
              "Wait for the PIM page to load"
            ];
    
            const response = {
              success: true,
              message: "PIM navigation tool executed successfully",
              steps: navigationSteps,
              target_module: "PIM",
              expected_url: "/web/index.php/pim/viewPimModule",
              note: "This tool provides navigation instructions for the PIM module. Requires user to be logged in first."
            };
    
            return {
              content: [
                {
                  type: "text",
                  text: `PIM Navigation Tool Response:
                  
    ✅ Tool: navigate_to_pim
    🎯 Target Module: PIM (Personal Information Management)
    🔗 Expected URL: ${LOGIN_CREDENTIALS.targetUrl}/web/index.php/pim/viewPimModule
    
    📋 Navigation Steps:
    ${navigationSteps.map((step, index) => `${index + 1}. ${step}`).join('\n')}
    
    💡 Note: This tool assumes the user is already logged in and has access to the navigation menu.
    The PIM module provides functionality for managing employee personal information, employment details, and related HR data.
    
    🔧 For browser automation integration, this tool can be extended to:
    - Verify user is logged in before navigation
    - Click the PIM menu item using Playwright
    - Wait for page load confirmation
    - Handle navigation errors or timeouts
    - Provide feedback on successful navigation`
                }
              ]
            };
    
          } catch (error) {
            throw new McpError(
              ErrorCode.InternalError,
              `PIM navigation tool failed: ${error instanceof Error ? error.message : String(error)}`
            );
          }
        }
  • src/tools.ts:179-236 (registration)
    The registration function for the 'navigate_to_pim' tool, called with the MCP server instance. Defines the tool name, description, input schema (empty), and inline handler.
    export function registerNavigateToPimTool(server: McpServer): void {
      server.tool(
        "navigate_to_pim",
        "Navigates to the PIM (Personal Information Management) page using the left-hand navigation menu. Assumes user is already logged in.",
        {},
        async () => {
          try {
            const navigationSteps = [
              "Locate the left-hand navigation menu",
              "Find the 'PIM' menu item in the navigation list",
              "Click on the 'PIM' link to navigate to the PIM module",
              "Wait for the PIM page to load"
            ];
    
            const response = {
              success: true,
              message: "PIM navigation tool executed successfully",
              steps: navigationSteps,
              target_module: "PIM",
              expected_url: "/web/index.php/pim/viewPimModule",
              note: "This tool provides navigation instructions for the PIM module. Requires user to be logged in first."
            };
    
            return {
              content: [
                {
                  type: "text",
                  text: `PIM Navigation Tool Response:
                  
    ✅ Tool: navigate_to_pim
    🎯 Target Module: PIM (Personal Information Management)
    🔗 Expected URL: ${LOGIN_CREDENTIALS.targetUrl}/web/index.php/pim/viewPimModule
    
    📋 Navigation Steps:
    ${navigationSteps.map((step, index) => `${index + 1}. ${step}`).join('\n')}
    
    💡 Note: This tool assumes the user is already logged in and has access to the navigation menu.
    The PIM module provides functionality for managing employee personal information, employment details, and related HR data.
    
    🔧 For browser automation integration, this tool can be extended to:
    - Verify user is logged in before navigation
    - Click the PIM menu item using Playwright
    - Wait for page load confirmation
    - Handle navigation errors or timeouts
    - Provide feedback on successful navigation`
                }
              ]
            };
    
          } catch (error) {
            throw new McpError(
              ErrorCode.InternalError,
              `PIM navigation tool failed: ${error instanceof Error ? error.message : String(error)}`
            );
          }
        }
      );
    }
  • src/tools.ts:241-246 (registration)
    Helper function that registers all tools, including navigate_to_pim, on the MCP server.
    export function registerAllTools(server: McpServer): void {
      registerPerformLoginTool(server);
      registerGetLoginCredentialsTool(server);
      registerTestConnectionTool(server);
      registerNavigateToPimTool(server);
    }
  • src/index.ts:28-28 (registration)
    Top-level call to register all tools (including navigate_to_pim) on the MCP server instance during server initialization.
    registerAllTools(server);
  • The navigate_to_pim tool is listed in the getAvailableTools() array for listing available tools.
    "navigate_to_pim"
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the navigation mechanism (left-hand menu) and prerequisite (user logged in), but doesn't mention potential side effects, error conditions, or what constitutes successful navigation. The behavioral context is adequate but minimal.

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?

Two concise sentences with zero waste: first states the action and mechanism, second provides crucial prerequisite. Every word earns its place, and the most important information (what the tool does) is front-loaded.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description covers the essential purpose and prerequisite. However, for a navigation tool with no annotations, it could benefit from mentioning what happens after navigation or how to verify success.

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 with 100% schema coverage, so the schema already fully documents the empty parameter set. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose and usage context.

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 ('navigates to') and target resource ('PIM page'), specifying it uses the left-hand navigation menu. It distinguishes from siblings like login tools by assuming user is already logged in, though it doesn't explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context for when to use ('Assumes user is already logged in'), which implicitly distinguishes from login-related siblings. However, it doesn't explicitly state when NOT to use or name specific alternatives like 'perform_login' for unauthenticated scenarios.

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/nieperdragon/custom_mcp'

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