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

namecheap-webui-mcp

by Microck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

namecheap_domains_list

Retrieve all domains from your Namecheap account displayed on the Domain List page for easy management.

Instructions

List domains visible in the Namecheap Domain List page.

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_domains_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
headedNoRun with a visible browser window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states it lists domains, but omits crucial details like whether prior login is required, if it is read-only, how many domains are returned, or whether it interacts with a web UI (implied by the 'headed' parameter).

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

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, making it concise but potentially underspecified. It front-loads the action but sacrifices useful detail for brevity.

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 tool's simplicity (one optional parameter, no output schema), the description should provide enough context for correct use. However, it lacks behavioral details and usage cues, making it incomplete for an agent to reliably invoke without additional context.

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 coverage is 100%, so the parameter 'headed' is fully described in the schema. The description adds no additional semantic context beyond the schema's 'Run with a visible browser window.' It does not explain why or when to set it.

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 lists domains from the Namecheap Domain List page. It uses a specific verb ('list') and identifies the resource ('domains') and source ('Domain List page'), distinguishing it from siblings like namecheap_dns_get_records.

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 like namecheap_domain_get_overview or namecheap_dashboard_list_options. It lacks context about prerequisites, intended use cases, or exclusions.

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