Loading ToolBench

Reading the current corpus…

domaindetails-mcp MCP server · C · ToolBench

domaindetails-mcp

github.com/simplebytes-com/domaindetails-mcp

Domain research toolkit for Claude Desktop and MCP clients. Provides comprehensive domain registration details, nameservers, contacts, and status information using RDAP protocol with WHOIS fallback.

2026-07-28+STDIO1 tools

60/100

Definition Quality77

Protocol Readiness45

Supportability41

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Single tool with complete schema and reasonable description. Naming follows verb_noun pattern (domain_lookup). Input schema properly typed with required fields and defaults. However, output schema is not documented in the tool definition, formatResult() exists but its return structure is not formally declared. Parameter descriptions are adequate but lack constraint details (e.g., valid domain formats, length limits). Error handling returns text-wrapped JSON but lacks actionable recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite being a read-only lookup.

Tools (1)

domain_lookupread onlysource verified77/100

Look up domain information using RDAP protocol with WHOIS fallback. Provides comprehensive domain registration details, nameservers, contacts, and status information.

Issues (5)

HIGHtool ↗

Output schema not documented. formatResult() returns structured data but the tool definition does not declare what fields clients should expect (domain, found, method, timestamp, status, nameservers, etc.). LLMs cannot plan downstream operations without knowing the response structure.

domain_lookup

MEDIUMconstrained-input ↗

Parameter descriptions lack format constraints. 'domain' parameter accepts any string but should specify valid formats (e.g., 'Valid domain name: 2-253 characters, alphanumeric and hyphens, no leading/trailing hyphens'). LLMs will pass invalid domains without guidance.

domain_lookup

MEDIUMrecovery-guide ↗

Error responses lack recovery guidance. When both RDAP and WHOIS fail, the tool returns a concatenated error message but does not suggest next steps (e.g., 'Domain may not exist, or both lookup services are temporarily unavailable. Try again in 30 seconds.'). Agents cannot determine if the error is retryable.

domain_lookup

Recommendations

Add a formal output schema to the tool definition: document all response fields (domain, found, method, timestamp, status, nameservers, registrar, created_date, updated_date, expires_date, contacts, fallback_used, primary_method_failed, primary_method_error, fallback_error) with types and descriptions.
Enhance the domain parameter description: 'The domain name to look up (2-253 characters, alphanumeric and hyphens, e.g., example.com). Must be a valid registered domain.'
Add error classification and recovery hints: 'If both methods fail, the domain may not exist, or lookup services are temporarily unavailable. Retry after 30 seconds or check domain spelling.'
Declare tool annotations in getToolDefinition(): add readOnlyHint: true and idempotentHint: true to signal safety properties to clients.
Document fallback behavior in the description: 'Attempts RDAP first (default) or WHOIS first (if prefer_whois=true). If the primary method fails or returns no results, automatically tries the fallback method. Response includes method and fallback_used flags to indicate which protocol succeeded.'

Score history

Overall score trend

First recorded score · v2 rubric

60/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	C	60	2026-07-28+	v2