Skip to main content
Glama
Sign In
namecheap-webui-mcp

namecheap-webui-mcp

by Microck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

namecheap_webui_login

Log into Namecheap web interface by submitting your username and password, optionally followed by a two-factor authentication code.

Instructions

Sign into Namecheap with username/password and optionally submit a 2FA code.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "namecheap_webui_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameNoNamecheap username or email for the initial login step.
passwordNoNamecheap password for the initial login step.
twoFactorCodeNoCurrent 2FA code for the second login step after credentials are accepted.
headedNoOpen a visible browser window when local GUI debugging is available.
timeoutMsNoHow long to wait for login completion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so description must disclose behaviors. It outlines login steps but omits outcomes (success/failure), side effects (rate limits), and prerequisites (headed for debugging).

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?

Single sentence, compact, no wasted words. Front-loaded with core action.

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?

Lacks behavioral details like post-login state, error messages, timeout behavior, and prerequisites. No output schema to compensate.

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?

Schema coverage is 100%, baseline 3. Description adds context like 'initial login step' and 'second login step', clarifying parameter ordering beyond schema names.

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

Purpose5/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: signing into Namecheap with username/password and optionally a 2FA code. This distinguishes it from siblings like import_cookies and query.

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

Usage Guidelines3/5

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

The description implies usage for login but provides no explicit guidance on when not to use it or alternatives (e.g., if cookies are already available).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools