Skip to main content
Glama

Name Whisper — ENS Intelligence Layer

by ai.namewhisper
OverviewDiscussionsAdmin

cancel_listing

DestructiveIdempotent

Cancel an active ENS name listing by submitting Seaport's cancel() on-chain.

Returns the unsigned Seaport cancel() transaction calldata. Your wallet signs and submits; once mined, Seaport marks the order invalid and no marketplace (NW, Grails, OpenSea) can fulfill it anymore.

Only the original seller (the order's offerer) can cancel. If you cross-posted to OpenSea, you signed a second 'opensea' variant of the listing — pass BOTH order hashes as alsoCancel so a single tx kills both variants atomically. alsoCancel takes at most 8 other hashes (do not repeat orderHash), all listings for the same name; the result lists every order the transaction cancels.

For cancelling offers you've made as a buyer, use cancel_offer instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderHashYesSeaport order hash of the listing to cancel (from get_name_details or the orderbook)
alsoCancelNoUp to 8 more of your listings FOR THE SAME NAME to cancel atomically in the same tx (e.g. the OpenSea-variant counterpart of an NW listing). Seaport.cancel() accepts an array — cancelling N orders costs barely more than cancelling one.
walletAddressYesWallet address of the seller. Must match the original offerer on the order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / alsoCancel / description
      Previous value: -"Sibling order hashes to cancel atomically in the same tx (e.g. the OpenSea-variant counterpart of an NW listing). Seaport.cancel() accepts an array — cancelling N orders costs barely more than cancelling one."New value: +"Up to 8 more of your listings FOR THE SAME NAME to cancel atomically in the same tx (e.g. the OpenSea-variant counterpart of an NW listing). Seaport.cancel() accepts an array — cancelling N orders costs barely more than cancelling one."
    • addedInput schema / properties / alsoCancel / maxItems
      Added value: +8
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=true, idempotent=true): it discloses that the tool returns unsigned calldata for the wallet to sign, that the effect is permanent order invalidation across NW/Grails/OpenSea, the authorization constraint (offerer only), and the atomic multi-cancel behavior with a max of 8 extra hashes.

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?

Front-loads the core action and return value, then layers constraints and the sibling routing in short, dense paragraphs. No filler 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?

No output schema exists, and the description compensates by describing the returned unsigned calldata and that the result enumerates every cancelled order. For a destructive, authorization-gated mutation, nothing essential is missing.

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 already 100%, so the baseline is 3; the description nonetheless adds operational meaning by explaining why alsoCancel exists (OpenSea variant), that it must not repeat orderHash, and that all hashes must belong to the same name.

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?

States a specific verb+resource (cancel an active ENS name listing) and the mechanism (submitting Seaport's cancel() on-chain). It explicitly differentiates from the sibling cancel_offer by stating that offers are cancelled elsewhere.

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?

Gives explicit when/when-not guidance: only the original seller/offerer can cancel, and buyer-side offers route to cancel_offer. It also explains the cross-posted OpenSea-variant scenario and how to handle it in one transaction.

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