Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ Promo Board Renewal (0.01 USDC)

promo_renew_listing

Add one more 24-hour campaign to your Promo Board listing, starting when the current one ends. Price: 0.01 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_renew_listing"}. Same tool over HTTP: https://yruz.one/api/promo/renew

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_renew_listing"
  }
}

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: exact price (0.01 USDC), x402 payment rails, invalid input refused before payment, failed runs never charged, and PaymentRequired returned without payment. It also implicitly explains the non-idempotent behavior declared in annotations, since each call queues another campaign.

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?

Purpose is front-loaded in the first clause, followed by price, failure semantics, and the alternate HTTP endpoint. A little dense (payment boilerplate plus invocation hint), but every sentence carries actionable information.

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?

Covers the payment/refusal/failure contract that matters most for a paid mutation, and explains the PaymentRequired return in the absence of an output schema. Minor gaps: it doesn't say what happens if the listing id no longer exists or whether multiple renewals can be stacked.

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 the schema already documents id (16-char listing id) and token (yzp_ owner token) with aliases. The description adds no extra meaning about either parameter, so the baseline of 3 is appropriate.

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?

States a specific verb and resource: it adds one more 24-hour campaign to an existing listing, and pins the timing ('starting when the current one ends'). That timing clause distinguishes it from promo_create_listing and promo_takeover_top_spot, though the description never names those siblings directly.

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?

Usage is only implied: the required id/token 'returned by /api/promo/create' signals this is for listings you already own and want to extend. There is no explicit statement of when to pick this over promo_create_listing or promo_takeover_top_spot, and no prerequisites beyond payment.

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