Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ Promo Board: get featured (discovery)

promo_get_featured
Read-onlyIdempotent

Discovery: the current GLOBAL TOP LINK of the YRUZ Promo Board and the next takeover minimum. Same data as GET https://yruz.one/api/promo/featured

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already establish that this is a safe, idempotent read operation. The description adds useful semantic context about the returned data and the external endpoint, but it does not disclose freshness, rate limits, auth requirements, or output format, so it only modestly extends 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences with no wasted wording. The key result is front-loaded in the first sentence, and the endpoint equivalence is supplementary rather than distracting.

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 parameterless, read-only discovery tool with rich annotations and no output schema, the description is largely sufficient. It could be slightly more complete by clarifying the format or units of the 'top link' and 'takeover minimum', but the essential call context is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there are no parameter semantics to clarify. Per the baseline for parameterless tools, a 4 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?

The description states a specific discovery result: the current global top link and next takeover minimum. This is clearer than the bare tool name and goes beyond tautology, but it does not explicitly distinguish the tool from close siblings such as promo_get_leaderboard or promo_takeover_top_spot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It labels the tool as 'Discovery' and gives an external API equivalent, but it never says when to use this instead of related tools like promo_get_leaderboard or promo_takeover_top_spot. No exclusions, prerequisites, or decision criteria are provided.

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