Skip to main content
Glama

operator_buy

Read-only

Buy a listed Operator: re-checks the listing on chain, then returns the ONE unsigned transaction the buyer's own wallet sends to Seaport (value = the price). Seaport moves the token and pays the seller in the same transaction, or neither. 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": {
      "listing_id": "<listing_id>",
      "buyer": "<buyer>"
    },
    "name": "operator_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYesthe 0x address of the buyer's wallet (it receives the Operator)
listing_idYesthe listing's id from operators_market

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 cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description explains the surprising part: despite being a "buy", nothing is signed or sent here, so a readOnly classification is coherent rather than contradictory. It also discloses atomicity ("moves the token and pays the seller in the same transaction, or neither") and the on-chain re-check, which no annotation conveys.

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 sentences, front-loaded with the action, then the failure/atomicity semantics and the crucial "nothing is signed or sent here" caveat. No filler and no restatement of the name or title.

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, read-only tool with no output schema, this is nearly complete, and it volunteers the return concept (one unsigned transaction) plus atomicity. Minor gap: it does not say what happens when the on-chain re-check fails (e.g., listing already filled or price changed), which matters for a non-idempotent purchase flow.

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 both parameters (buyer, listing_id) are already documented in the schema, including where the listing id comes from. The description adds no syntax or format detail beyond that; the "value = the price" note concerns the returned transaction, not an input.

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 ("Buy a listed Operator") and immediately specifies the mechanism: re-checks the listing on chain, returns one unsigned Seaport transaction, with value equal to the price. This clearly separates it from operator_sell, operator_list, and operators_market without the agent needing to open a schema.

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?

The context is clear: the caller has a listing id (from operators_market) and a buyer wallet, and this tool initiates a purchase. It does not explicitly state when-not to use it or name a sibling alternative, but the buying scenario is unambiguous from the first clause.

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