Prepare the on-chain Seaport cancel transaction for an active order. Only the order's offerer can execute it (Seaport enforces msg.sender == offerer), so the calldata is safe to return. After it confirms, POST { txHash } to the confirm endpoint to update the book.
| Name | Required | Description | Default |
|---|---|---|---|
| orderHash | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral burden. It discloses that the tool returns calldata rather than executing the cancellation, that Seaport enforces msg.sender == offerer, and that a subsequent confirm step is required. This gives an agent a solid understanding of the safety and workflow, though it does not detail failure modes or invalid-order handling.
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?
Three concise sentences with no filler. Each sentence contributes: what the tool does, an authorization/safety note, and the post-confirmation workflow. It is well-structured and front-loaded.
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?
For a single-parameter tool with no output schema and no annotations, the description covers the core invocation context: purpose, authorization restriction, return nature, and next step. It could be more complete by describing the expected orderHash format, but overall it gives an agent enough to act correctly.
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?
The schema has 0% description coverage and the description does not explain the orderHash parameter's format or meaning beyond the tool's purpose. While 'orderHash' is reasonably self-explanatory, the description adds no explicit value to the schema, so an agent must infer details from the parameter name alone.
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 clearly identifies the action: preparing an on-chain Seaport cancel transaction for an active order. It distinguishes itself from sibling tools like prepare_listing and prepare_purchase by the cancel verb and Seaport context.
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 makes the intended use obvious: cancel an active Seaport order. It also includes a critical constraint—only the offerer can execute—and provides the follow-up step of posting the txHash after confirmation. It does not explicitly name sibling alternatives or exclusion conditions, but the context is clear enough.
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.
