Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ Promo Board: get listing (discovery)

promo_get_listing
Read-onlyIdempotent

Discovery: one Promo Board listing with its campaigns and takeovers. Same data as GET https://yruz.one/api/promo/listing

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>"
    },
    "name": "promo_get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYeslisting id (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds useful context that the result includes campaigns and takeovers, but it does not cover auth requirements, rate limits, or response shape details beyond that inclusion note.

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 short and front-loads the core purpose. The second sentence about the equivalent GET endpoint is arguably redundant, but overall the definition remains efficient.

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 simple one-parameter read tool with full schema coverage and clear annotations, the description provides enough context by stating what related data is returned. It does not fully explain the return format, but no output schema exists and the tool itself is straightforward.

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% for the single required id parameter, so the schema fully documents it. The description does not add syntax, format, or semantic detail about the id beyond what the schema already provides, making the baseline 3 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?

The description clearly states that it retrieves one Promo Board listing, including its campaigns and takeovers. This is a specific verb+resource, though it does not explicitly differentiate the tool from siblings such as promo_search_listings or promo_get_featured.

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 word "Discovery" implies a lookup use case, and the singular "one listing" hints at retrieval by ID rather than search. However, there is no explicit guidance on when to use this versus promo_search_listings, promo_get_featured, or promo_get_campaign_history.

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