Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ Promo Board Top Link Takeover (0.05 USDC)

promo_takeover_top_spot

Take over the GLOBAL TOP LINK of the YRUZ Promo Board for 24 hours with your live listing. The price is the server minimum (current top price plus the increment), quoted exactly in the 402; a stale quote is refused before it settles. Price: 0.05 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"promo_takeover_top_spot"}. Same tool over HTTP: https://yruz.one/api/promo/takeover

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": {
      "id": "<id>",
      "token": "<token>"
    },
    "name": "promo_takeover_top_spot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYeslisting id returned by /api/promo/create, 16 characters (required), aliases listing, listing_id
tokenYesowner_token returned by /api/promo/create, starts with yzp_ (required), alias owner_token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"listing id (required), from promo_create_listing"New value: +"listing id returned by /api/promo/create, 16 characters (required), aliases listing, listing_id"
    • changedInput schema / properties / token / description
      Previous value: -"owner_token (required), from promo_create_listing"New value: +"owner_token returned by /api/promo/create, starts with yzp_ (required), alias owner_token"
  2. Added

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the 24-hour duration, that price is the server minimum quoted in the 402, that stale quotes are refused before settlement, that invalid input is refused before payment and failed runs are never charged, and that an unauthenticated call returns PaymentRequired. These are exactly the behaviors an agent needs to reason about cost and side effects.

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?

Front-loaded with purpose, then pricing, then payment mechanics, then invocation hint. Slightly redundant — the 0.05 USDC price appears in both the title and body, and the payment/no-charge guarantees are restated twice — but nearly every sentence earns its place.

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 paid, non-idempotent mutation with a 2-param schema and no output schema, the description covers cost, failure modes, payment flow, and the alternate HTTP endpoint. What's missing is any statement of what a successful call returns (e.g., the new top-link record), which matters since there is no output schema.

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%, with id and token fully documented in the schema including origins and aliases. The description only alludes to 'your live listing' and adds no format or sourcing detail beyond the schema, so baseline 3 applies.

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 states a specific verb+resource+scope: take over the GLOBAL TOP LINK of the YRUZ Promo Board for 24 hours with your live listing. It is clearly distinguishable from renewal/listing-creation siblings by the 'top link takeover' framing, though it never names a sibling to contrast with.

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?

It implies prerequisites (you need a live listing, paid via x402) and points to get_example for invocation details, but never explicitly says when to choose this over promo_renew_listing or promo_get_pricing, nor what happens when you already hold the top spot.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All YRUZ x402 tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources