Delete a notification subscription. Two-step like subscribe_notifications: call without signature to get the message to sign. chainId is signed over and verified on that chain. Signed messages are single-use.
| Name | Required | Description | Default |
|---|---|---|---|
| wallet | Yes | ||
| chainId | Yes | chain the wallet signs on; it is part of the signed message | |
| signature | No | ||
| timestamp | Yes | ||
| subscriptionId | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses several non-obvious behaviors: the two-step signing flow, that `chainId` is signed over and verified on that chain, and that signed messages are single-use. It could add more about response behavior or failure modes, but it covers the most important traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences long and front-loaded with the core purpose. Every sentence earns its place: the deletion action, the two-step procedure, the chain verification, and the single-use constraint. There is no redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is moderately complex due to the two-step signing flow, but the description explains the overall workflow well. However, there is no output schema and no annotation fallback, and the description does not explain what the first step returns beyond "the message to sign," nor does it clarify the semantics of required parameters like `timestamp` and `subscriptionId`. It is adequate but leaves clear gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 20%, with just `chainId` described. The description adds useful context for `chainId` and the optional `signature`, but it does not explain `wallet`, `timestamp`, `subscriptionId`, or how the signature produced in step one is used in step two. Parameter names and patterns provide some hints, but this is insufficient for a signed two-step flow.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: "Delete a notification subscription." This clearly identifies the tool's purpose and distinguishes it from the sibling subscribe_notifications by referencing the same two-step flow while noting the deletion action. There is no ambiguity about what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear invocation context: it is a two-step operation and the agent should call without `signature` first to obtain the message to sign. It does not explicitly name alternatives or when-not-to-use conditions, but the deletion purpose and reference to subscribe_notifications provide clear enough guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools map cleanly to distinct resources and actions, with the prepare_* group differentiated by their operation suffix. The main ambiguity is get_listing_details, whose description says 'one order' while the name implies a listing, so it could be confused with get_orders or get_listings.
All tool names are lowercase snake_case and follow a verb-first shape using get/list/search/prepare/subscribe/unsubscribe, which is predictable. Minor inconsistencies exist: get_ and list_ are both used for read operations, and prepare_finalize/prepare_cancel pair the prepare_ prefix with a verb rather than a noun.
15 tools is at the high end but each one earns its place: market discovery, order listing, transaction preparation, purchase/offer/cancel flows, Basename finalization, and notification management. There is no obvious padding or missing category that would make the count feel bloated.
The core marketplace lifecycle is well covered: create listings/offers, buy/accept, cancel, finalize, and query listings/orders/positions/trades/names/notifications. The most notable gap is a lack of a synchronous, first-class query for offers received on an owned listing or position; discovery of incoming offers relies on notifications or knowing the bidder's address.
