Skip to main content
Glama

operator_sell

Read-only

Step one of selling an Operator you hold: reads that your wallet holds the token, whether Seaport may move it (if not, returns the one approval transaction your wallet sends first) and your Seaport counter, then returns the EIP-712 typed data your wallet signs (eth_signTypedData_v4: a signature, not a transaction). Step two is operator_list with the listing and that signature. 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>",
      "token_id": "<token_id>",
      "price_eth": "<price_eth>"
    },
    "name": "operator_sell"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNohow long the listing stays open (1 to 180, default 30)
chainNo4663 (default, real) or 998 (testnet rehearsal)
walletYesthe 0x address of the wallet that holds the Operator
token_idYesthe Operator's token id
price_ethYesthe price in the chain's native coin, a plain decimal like 0.05

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds real behavioral context beyond them: it reads wallet ownership, checks whether Seaport may move the token, may return a single approval transaction the wallet must send first, and returns typed data for eth_signTypedData_v4 rather than a transaction. The claim that nothing is signed or sent is consistent with readOnlyHint, so there is no contradiction.

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?

The description is front-loaded with the tool's role and the step-one/step-two split, then the return payload, then the safety disclaimer. Every clause carries information an agent needs; there is no filler or repetition of the name.

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?

Although there is no output schema, the description explains what comes back (approval transaction if needed, typed data for signing) and what does not happen (no signing, no sending). For a read-only preparation step with fully documented parameters, nothing material 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% and every parameter (wallet, token_id, price_eth, days, chain) is already documented in the schema, including the enum values and ranges. The description adds no parameter-level meaning such as price formatting or chain selection implications, so the baseline of 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?

The description states a specific verb and resource: it reads wallet token holdings, Seaport approval state and the Seaport counter, then returns EIP-712 typed data for signing. It explicitly distinguishes itself from the sibling operator_list, which is named as 'step two', so an agent can route between the two without inspecting 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?

Usage is spelled out as an explicit two-step workflow: call this first, then call operator_list with the listing and the returned signature. The boundary condition is also stated ('Nothing is signed or sent here'), so the agent knows this tool does not complete a sale.

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