Skip to main content
Glama

operator_list

Idempotent

Step two of selling: publish a listing your wallet signed (the listing operator_sell returned, and the signature). The deck checks it the only way that counts, by simulating its fill on chain; a listing Seaport would refuse is refused here with the reason. Signed in only.

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": {
      "listing": "<listing>",
      "signature": "<signature>"
    },
    "name": "operator_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listingYesthe listing object operator_sell returned, unchanged
signatureYesthe 0x signature your wallet made over operator_sell's typed data

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare a non-read-only, idempotent, open-world write, and the description adds real context: validation happens by simulating the fill on chain and failures return the reason Seaport would refuse. It omits what a success response contains and any rate limits, but the added disclosure goes well beyond the annotations.

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?

Two compact sentences, front-loaded with the workflow position and immediately followed by what happens during validation. No filler or repeated annotation content.

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?

For a two-parameter mutation with no output schema, the description covers inputs, sequencing, auth, and failure behavior. Success-path output expectations are the only notable gap, and with no output schema that is a minor omission.

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 coverage is 100% and the description largely restates what the schema already says (listing from operator_sell, 0x signature over the typed data). Useful confirmation, particularly 'unchanged', but no new syntax or format detail beyond the schema.

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 ('publish a listing') and anchors it to the sibling workflow ('Step two of selling' after operator_sell). An agent can tell immediately this is the post-signature publish step, not the signing step itself.

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?

Clearly positions the tool after operator_sell and requires the returned listing plus signature, and notes 'Signed in only' as an auth precondition. It doesn't state explicit failure/retry guidance or when to re-sign instead, but the sequencing context is strong.

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