Skip to main content
Glama

Name Whisper — ENS Intelligence Layer

by ai.namewhisper
OverviewDiscussionsAdmin

batch_create_listings

Bulk-list up to 500 ENS names for sale on NameWhisper in one signing flow.

Returns an array of unsigned Seaport OrderComponents payloads. The caller's wallet signs them all in one EIP-712 bulk signature (SIP-6), then POSTs the signed orders back to https://namewhisper.ai/api/orderbook/submit-bulk (up to 500 per request) to store.

NW-native only — listings stay on NameWhisper. Cheaper UX than calling create_listing in a loop (one wallet popup vs N).

Per-name errors (invalid label, zero price) are collected in the 'errors' field instead of aborting the whole batch — partial success is normal.

Requires operator approval on the ENS token contract (NameWrapper or BaseRegistrar) — do this once per wallet via approve_operator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listingsYesArray of { name, priceEth }. Per-item validation (empty name, non-positive price) is collected in the errors array rather than rejecting the whole batch.
walletAddressYesWallet address of the seller. Must own all the names.
durationSecondsNoListing duration in seconds (applied to every name, default: 30 days, at most 31536000: one year)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / durationSeconds / description
      Previous value: -"Listing duration in seconds (applied to every name, default: 30 days)"New value: +"Listing duration in seconds (applied to every name, default: 30 days, at most 31536000: one year)"
    • changedInput schema / properties / durationSeconds / maximum
      Previous value: -9007199254740991New value: +31536000
  2. Changed1 schema field changed
    • changedInput schema / properties / listings / maxItems
      Previous value: -10New value: +500
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, idempotent=false, destructive=false) by describing the exact workflow: returns unsigned Seaport OrderComponents, caller signs via EIP-712 bulk signature (SIP-6), then POSTs signed orders to a named endpoint. It also discloses partial-failure semantics (per-name errors collected, batch not aborted) and the required operator approval — rich context the annotations cannot convey.

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

Conciseness4/5

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

Front-loads the core action, then layers workflow, alternative, error behavior, and prerequisite in distinct paragraphs. Slightly verbose with some overlap between the 500-item mention in prose and schema, but every paragraph carries actionable information.

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?

Despite no output schema, the description explains the return value (array of unsigned Seaport OrderComponents), the post-call signing/submission step, and the error-field behavior on partial failure. For a complex multi-step batch mutation, nothing essential is missing.

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 description coverage is 100%, so the schema already documents listings, walletAddress, and durationSeconds. The description reinforces the 500-item cap and the per-item error-collection behavior, but adds no new syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

Specific verb+resource with scope: bulk-list ENS names for sale on NameWhisper in one signing flow. It explicitly differentiates itself from the sibling create_listing by contrasting the bulk single-popup flow with a per-name loop, so an agent can choose without opening either schema.

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?

States the condition for use (bulk listing, NW-native only), names the alternative (create_listing in a loop) and why this is preferred, and gives the prerequisite (operator approval via approve_operator). It also flags that partial success is normal, which shapes how the agent should interpret results.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources