Skip to main content
Glama

Name Whisper — ENS Intelligence Layer

by ai.namewhisper

create_listing

List an ENS name for sale on NameWhisper's marketplace via Seaport 1.6.

Returns an unsigned Seaport OrderComponents payload (plus EIP-712 domain/types) that the caller's wallet signs. After signing, POST the { orderComponents, signature, label, orderType: 'listing' } payload to https://namewhisper.ai/api/orderbook/submit (authenticated) to store the order.

Fee structure: 1% marketplace fee baked into the order as a Seaport consideration item (seller-paid, not added on top).

NW-native only — MCP listings stay on NameWhisper. If you want your listing on OpenSea too, list it separately through their interface.

Requires the wallet to have approved NameWrapper (for wrapped names) or BaseRegistrar (for unwrapped) as an operator first. Use approve_operator if needed.

Tip: Use get_valuation first to price competitively. Use get_name_details to confirm the name is unwrapped vs wrapped before listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesENS name to list (e.g. "coffee.eth")
priceEthYesTotal listing price in ETH (buyer pays this; seller receives it minus the 1% marketplace fee)
walletAddressYesWallet address of the seller. Must own the name.
durationSecondsNoListing duration in seconds (default: 30 days / 2592000)

TDQS

A4.9/5.0
Behavior5/5

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

Discloses return type (unsigned Seaport OrderComponents), next steps (sign and submit to URL), fee structure (1% seller-paid), and requirement for operator approval. No annotations contradict; description adds significant behavioral context.

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?

Well-structured, front-loaded with purpose, then step-by-step explanation, fee, limitation, prerequisites, and tips. No wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive for a 4-param tool with no output schema. Describes the output, usage workflow, fees, and limitations. All necessary context provided.

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 100% with clear descriptions. The priceEth description explains the fee, which is also reiterated in the description. Adds minor extra value beyond schema.

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?

Clear verb+resource: 'List an ENS name for sale on NameWhisper's marketplace via Seaport 1.6.' Distinguished from siblings like batch_create_listings and cancel_listing.

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

Usage Guidelines5/5

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

Explicit when to use (list on NameWhisper) and when not (NW-native only; for OpenSea use their interface). Provides prerequisites (approve operator) and tips (use get_valuation, get_name_details).

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

All Name Whisper — ENS Intelligence Layer toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes with detailed descriptions, but some pairs (e.g., search_ens_names vs enumerate_entities, batch_purchase vs sweep) could cause confusion due to overlapping functionality. The descriptions help differentiate, but the large number of tools increases ambiguity risk.

Naming Consistency5/5

All tool names use consistent snake_case with a verb_noun pattern (e.g., get_name_details, set_ens_records, batch_create_listings). Naming conventions are uniform and predictable, making it easy to infer tool purpose from the name.

Tool Count4/5

With 44 tools, the server is quite comprehensive, covering a wide range of ENS operations. While this exceeds the typical 3-15 tool count, the scope of the domain (marketplace, registration, agent identity, etc.) justifies the number, and tools are well-organized into logical groups.

Completeness5/5

The tool surface covers the full lifecycle of ENS names: registration, renewal, wrapping, transfers, marketplace actions (listings, offers, purchases), record management, subnames, agent identity, and market intelligence. No obvious gaps are present for an ENS intelligence platform.

Resources