Skip to main content
Glama

operator_cancel

Read-onlyIdempotent

Cancel every Operator listing your wallet signed, at once: returns the ONE unsigned transaction (Seaport incrementCounter) your wallet sends on that chain. Each listing signed the counter it was made under, so a new counter voids them all; operators_market then shows them closed. Moving the token also ends its listing. Nothing is signed or sent here.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wallet": "<wallet>"
    },
    "name": "operator_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo4663 (default, real) or 998 (testnet rehearsal)
walletYesthe 0x address of the wallet whose listings to cancel

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description is consistent while adding the crucial non-obvious behavior: the tool does not itself cancel anything, it returns an unsigned transaction the wallet must send, and 'Nothing is signed or sent here.' It also discloses the downstream effect (operators_market shows listings closed), which 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.

Conciseness5/5

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

Three tight sentences, front-loaded with the action and scope, then the mechanism, then the safety caveat. No filler; each clause carries information an agent needs.

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

Completeness4/5

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

With no output schema, the description compensates by describing the return value (a single unsigned transaction) and the post-condition. It is nearly complete for a two-parameter tool, though it could say more about what the caller should do with the returned transaction or whether repeated calls are safe.

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 both parameters (wallet address, chain enum with default 4663 and testnet 998) are already documented in the schema. The description adds no further parameter-level meaning such as address format constraints or chain-specific behavior, so the baseline of 3 applies.

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 and resource with explicit scope: 'Cancel every Operator listing your wallet signed, at once.' It also names the concrete artifact returned (the ONE unsigned Seaport incrementCounter transaction), which distinguishes it from siblings like operator_list and operators_market.

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

Usage Guidelines4/5

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

Explains the mechanism that makes the tool work (each listing is bound to the counter it was signed under, so a new counter voids them all) and notes an alternative path ('Moving the token also ends its listing'). It stops short of an explicit when-to-use-this-vs-that rule against a named sibling, so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources