Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ Promo Board Listing (0.02 USDC)

promo_create_listing

List a link, API, x402 endpoint, MCP server or dataset on the YRUZ x402 Promo Board for exactly 24 hours (directory, leaderboards, machine-readable catalogue). Send title and url; category and type are optional. The destination is checked before payment and a refused link is not charged. Returns the listing id and an owner_token: keep both for promo_renew_listing and promo_takeover_top_spot. Price: 0.02 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_create_listing"}. Same tool over HTTP: https://yruz.one/api/promo/create?title=My+x402+API&url=https%3A%2F%2Fexample.com&category=api&type=api&description=What+it+does%2C+in+one+sentence

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": {
      "title": "<title>",
      "url": "<url>"
    },
    "name": "promo_create_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL to promote, https:// is added when missing (required), aliases link, website; with an agent Bearer token or a profile x-auth-token it defaults to your YRUZ profile
typeNoone of website, api, x402-endpoint, mcp-server, dataset, developer-tool, agent-service, open-source, other (default: guessed from the URL)
titleYeslisting title, 3-120 characters (required), alias name
categoryNoone of api, x402, mcp, data, ai, devtools, crypto, saas, open-source, media, other (default other; synonyms such as tools, dataset, mcp-server are mapped)
providerNodisplay name, up to 80 characters, optional
descriptionNoup to 300 characters, optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / category / examples
      Added value: +[
+  "api"
+]
    • addedInput schema / properties / description / examples
      Added value: +[
+  "What it does, in one sentence"
+]
    • addedInput schema / properties / title / examples
      Added value: +[
+  "My x402 API"
+]
    • addedInput schema / properties / type / examples
      Added value: +[
+  "api"
+]
    • addedInput schema / properties / url / examples
      Added value: +[
+  "https://example.com"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"public http(s) URL to promote, https:// is added when missing (required), aliases link, website"New value: +"public http(s) URL to promote, https:// is added when missing (required), aliases link, website; with an agent Bearer token or a profile x-auth-token it defaults to your YRUZ profile"
  3. Changed7 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"one of api, x402, mcp, data, ai, devtools, crypto, saas, open-source, media, other (required)"New value: +"one of api, x402, mcp, data, ai, devtools, crypto, saas, open-source, media, other (default other; synonyms such as tools, dataset, mcp-server are mapped)"
    • changedInput schema / properties / description / description
      Previous value: -"up to 300 characters"New value: +"up to 300 characters, optional"
    • changedInput schema / properties / provider / description
      Previous value: -"display name, up to 80 characters"New value: +"display name, up to 80 characters, optional"
    • changedInput schema / properties / title / description
      Previous value: -"title, 3-120 characters (required)"New value: +"listing title, 3-120 characters (required), alias name"
    • changedInput schema / properties / type / description
      Previous value: -"one of website, api, x402-endpoint, mcp-server, dataset, developer-tool, agent-service, open-source, other"New value: +"one of website, api, x402-endpoint, mcp-server, dataset, developer-tool, agent-service, open-source, other (default: guessed from the URL)"
    • changedInput schema / properties / url / description
      Previous value: -"public http(s) URL (required)"New value: +"public http(s) URL to promote, https:// is added when missing (required), aliases link, website"
    • changedInput schema / required
      Previous value: -[
-  "title",
-  "url",
-  "category"
-]New value: +[
+  "title",
+  "url"
+]
  4. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses crucial behavior: 24-hour listing duration, URL validation before payment, no charge for refused links or failed runs, 0.02 USDC x402 payment with no account/API key, PaymentRequired without payment, and the returned listing id plus owner_token. The write behavior is consistent with readOnlyHint=false and destructiveHint=false.

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 action and includes only relevant operational details, but it is fairly dense and somewhat repetitive around payment/refusal behavior. It remains readable and useful rather than padded.

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

Completeness5/5

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

For a paid, mutation-style listing tool with no output schema, the description covers what is created, duration, payment flow, validation and failure charging rules, authentication/payment prerequisites, error behavior, and return values. An agent has enough context to invoke it correctly.

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 description coverage is 100%, so the schema already documents all six parameters, including aliases, defaults, and allowed values. The description reinforces required title/url and optional category/type, but adds no parameter semantics beyond what the schema provides.

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?

The description uses a specific verb and resource: list a link, API, x402 endpoint, MCP server or dataset on the YRUZ x402 Promo Board. It also states the duration and surface (directory, leaderboards, catalogue), making it easy to distinguish from sibling promo retrieval/renewal tools.

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?

It clearly explains when to use the tool and names promo_renew_listing and promo_takeover_top_spot as follow-on tools that need the returned owner_token. It does not explicitly say when not to use it or name a create-vs-search alternative, so it falls short of a full when/when-not/alternatives statement.

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