Skip to main content
Glama

operators_market

Read-only

The open listings of Cubicle Operators (ERC-721) on Seaport 1.6, peer to peer: each listing's token, price and seller, re-checked NOW by simulating its fill on chain (a sold, moved, cancelled or ended listing says so). chain 4663 = the live collection on Robinhood Chain (real ETH); 998 = Test Operators on HyperEVM testnet, to rehearse (anyone may mint one). Read only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "operators_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo4663 (default, real) or 998 (testnet rehearsal)
token_idNooptional: only this token's listings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description adds important behavior: listings are re-checked NOW by simulating an on-chain fill, and sold, moved, cancelled or ended listings are reported as such. This tells the agent that results reflect fresh chain state rather than stale indexed data. It does not cover pagination, result limits, or failure modes, but the added behavioral context is substantial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is front-loaded with the core purpose and then supplies chain and verification details efficiently. It is dense but mostly earns its length; a small amount of punctuation and phrasing could make it easier to scan.

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 read-only listing tool with no output schema, the description explains the returned listing fields, the chain meanings, and the freshness guarantee. It is nearly complete, though it omits operational details such as pagination or whether empty results are indicated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes further by explaining what chain 4663 and 998 represent: the live Robinhood Chain collection with real ETH versus the HyperEVM testnet for rehearsal. Token_id is left mostly to the schema, limiting this to a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource: open Cubicle Operators ERC-721 listings on Seaport 1.6, with token, price, seller and live fill-simulation checks. It is specific enough to distinguish this from a general price or order book tool, but it does not explicitly name a sibling alternative for comparison.

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

Usage Guidelines3/5

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

The description provides context for the two chains, including that 998 is a testnet for rehearsal, which implies when to use each. However, it does not explicitly say when to choose this tool over siblings such as operator_list, price, or book_depth, nor does it state exclusions.

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