Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ Promo Board: search listings (discovery)

promo_search_listings
Read-onlyIdempotent

Discovery: search the YRUZ Promo Board listings (live by default) with their 24 h campaign, countdown and top-link status. Same data as GET https://yruz.one/api/promo/listings

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "promo_search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNotext in title, description or host
pageNopage, 1-100
typeNoresource type
statusNoactive (default), expired or all
categoryNocategory id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the bar is low. The description still adds useful context: results are live by default and include campaign/countdown/top-link fields, which tells the agent what it will get back. Pagination behavior is not mentioned, but that is minor given the annotation coverage.

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?

Two efficient sentences with the purpose front-loaded. The trailing 'Same data as GET …' is mildly redundant but does help users cross-reference the underlying API.

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 five-optional-parameter read-only search tool with no output schema, the definition supplies enough: what is searched, default liveness, and the notable returned fields. Missing only pagination/result-count behavior, which is a small gap.

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% and each parameter has its own description, so the schema carries the burden. The description adds only marginal semantics ('live by default' mirrors the status='active' default already in the schema) and no search-syntax details for q.

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 ('search') and resource ('YRUZ Promo Board listings') plus the data returned (24 h campaign, countdown, top-link status). It is clear what the tool does, though it never names a sibling like promo_get_featured or promo_get_leaderboard 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?

The 'Discovery:' prefix implies this is the broad search entry point, and 'live by default' hints at default scoping. However, there is no explicit when-to-use/when-not guidance and no mention of alternatives such as promo_get_listing for a single record.

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