Skip to main content
Glama

list_seat

Read-only

$0.09 = priority ping-verify + a seat on https://openclawproductions.com/verified after you pass. Price $0.09 (90000 atomic USDC on Base). Pays via x402. Offer: List Seat intro, $0.08 for the first call per wallet (list price $0.09). Code OCP-AO1. Path GET /api/v1/listseat-intro. Limit 1 per wallet, 50 total. Ends 2026-12-15.

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": {
      "origin": "<origin>"
    },
    "name": "list_seat"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYesPublic origin URL to enqueue for ping-verify.
contactNoOptional contact string. Not required for enqueue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

The description does add real behavioral context the annotations omit: the call is paid ($0.09 / 90000 atomic USDC on Base), settles via x402, and is capped at one per wallet and fifty total with a deadline. But it contradicts readOnlyHint=true by describing a purchase that grants 'a seat' and an action that enqueues a verification job — both state-creating. It also leaves 'ping-verify' and 'after you pass' undefined, so the agent cannot tell what happens on failure or whether payment is taken before verification.

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

Conciseness2/5

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

The first thing the reader gets is a price tag, then a URL, then a second restatement of the price in atomic units, then a promo code, path, and expiry date. Pricing is repeated twice and the promotional strings ('Offer: List Seat intro', 'Code OCP-AO1') consume space that should carry function. It is dense but not front-loaded on what the tool does.

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

Completeness2/5

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

For a paid, externally-facing action with no output schema, the description should explain what verification entails, what a pass versus a fail means for the caller, and whether the seat is granted synchronously. None of that is present, and the readOnly/openWorld annotations leave the side-effect profile ambiguous given the purchase semantics. What remains is a price sheet, not a specification.

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%, so both parameters (origin, contact) are already documented in the schema and a baseline of 3 applies. The description adds nothing about their meaning — the only URL it mentions, https://openclawproductions.com/verified, is the destination seat page, not the origin argument, and 'contact' is never addressed. It neither clarifies nor misleads on parameters.

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

Purpose3/5

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

The description says what the offer yields — 'priority ping-verify + a seat ... after you pass' — which is a recognizable verb+outcome, but it is framed as an ad headline rather than a statement of tool function and never says plainly that it enqueues an origin for verification. It gives no differentiation from any of the sibling tools. The purpose is inferable but requires the agent to decode marketing copy.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative. The constraints that are present — 'Limit 1 per wallet, 50 total', 'Ends 2026-12-15', promo code 'OCP-AO1' — are eligibility and pricing rules, not invocation guidance. The agent learns what it costs but not when this tool is the right choice.

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