Skip to main content
Glama
nieperdragon

MCP Login Server

by nieperdragon

get_login_credentials

Retrieve authentication credentials for localhost web applications to automate login processes with browser automation tools.

Instructions

Returns the login credentials that will be used for authentication to http://localhost

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The asynchronous handler function that implements the core logic of the get_login_credentials tool. It constructs and returns a structured MCP response containing the login credentials from the LOGIN_CREDENTIALS constant.
        async () => {
          return {
            content: [
              {
                type: "text",
                text: `Login Credentials:
                
    đŸŽ¯ Target URL: ${LOGIN_CREDENTIALS.targetUrl}
    👤 Username: ${LOGIN_CREDENTIALS.username}
    🔑 Password: AIWorkshopJuly!25
    
    â„šī¸ These credentials are configured for the OrangeHRM system running on localhost.`
              }
            ]
          };
        }
      );
  • src/tools.ts:94-116 (registration)
    The registration function that adds the get_login_credentials tool to the MCP server. It calls server.tool() with the tool name, description, empty input schema ({}), and the handler function.
    export function registerGetLoginCredentialsTool(server: McpServer): void {
      server.tool(
        "get_login_credentials",
        "Returns the login credentials that will be used for authentication to http://localhost",
        {},
        async () => {
          return {
            content: [
              {
                type: "text",
                text: `Login Credentials:
                
    đŸŽ¯ Target URL: ${LOGIN_CREDENTIALS.targetUrl}
    👤 Username: ${LOGIN_CREDENTIALS.username}
    🔑 Password: AIWorkshopJuly!25
    
    â„šī¸ These credentials are configured for the OrangeHRM system running on localhost.`
              }
            ]
          };
        }
      );
    }
  • Helper constant defining the login credentials (username, password, target URL) that are exposed by the get_login_credentials tool.
    export const LOGIN_CREDENTIALS = {
      username: "admin",
      password: "AIWorkshopJuly!25",
      targetUrl: "http://localhost"
    };
  • src/tools.ts:243-243 (registration)
    Invocation of the registration function within registerAllTools, ensuring the tool is registered when all tools are set up.
    registerGetLoginCredentialsTool(server);
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It states what the tool returns but doesn't disclose critical traits like whether credentials are stored securely, if this is a read-only operation, potential rate limits, or error conditions (e.g., missing credentials).

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 function and target. It's front-loaded with the core action ('Returns the login credentials') and includes necessary context ('for authentication to http://localhost') without any wasted words.

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 tool handling sensitive authentication data with no annotations and no output schema, the description is insufficient. It lacks details on return format (e.g., structured object vs. plain text), security implications, error handling, or how it integrates with sibling authentication tools, leaving significant gaps for an agent.

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 description coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose without redundant parameter details, meeting the baseline for parameter-less tools.

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 with a specific verb ('Returns') and resource ('login credentials'), and specifies the authentication target ('to http://localhost'). However, it doesn't explicitly differentiate from sibling tools like 'perform_login' or 'test_connection', which prevents a perfect score.

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. The description doesn't mention prerequisites (e.g., whether credentials must be pre-configured), timing (e.g., before or after login attempts), or relationships to sibling tools like 'perform_login' or 'test_connection'.

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