Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ DependencyPulse Release Compare (0.008 USDC)

deps_compare_releases
Read-onlyIdempotent

What changes between two releases of a package, from registry metadata: dependencies added, removed and re-ranged, licence change, deprecation, publish dates and the releases in between, and which OSV advisories the upgrade fixes, introduces or leaves open. Registry metadata only: a source-code diff is not claimed. Price: 0.008 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":"deps_compare_releases"}. Same tool over HTTP: https://yruz.one/api/deps/compare?ecosystem=npm&name=lodash&from=4.17.15&to=4.17.21

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": {
      "name": "<name>",
      "from": "<from>"
    },
    "name": "deps_compare_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNotarget version (default: latest)
fromYescurrent version (required), e.g. 4.17.15
nameYespackage name (required)
ecosystemNonpm (default), pypi or composer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / ecosystem / examples
      Added value: +[
+  "npm"
+]
    • addedInput schema / properties / from / examples
      Added value: +[
+  "4.17.15"
+]
    • addedInput schema / properties / name / examples
      Added value: +[
+  "lodash"
+]
    • addedInput schema / properties / to / examples
      Added value: +[
+  "4.17.21"
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld/non-destructive, and the description still adds substantial behavioral detail beyond them: price (0.008 USDC), x402 payment mechanics with no account or API key, invalid input refused before payment, failed runs never charged, and the x402 PaymentRequired response when unpaid. It also gives the equivalent HTTP endpoint for callers outside MCP.

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?

Front-loaded with the purpose and the 'no source-code diff' caveat before any commercial or invocation detail. The payment paragraph is dense but every clause (price, method, refund policy, PaymentRequired) carries decision-relevant information; the trailing HTTP URL is auxiliary but short.

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?

With no output schema, the description compensates by enumerating the returned fields, and for a 4-parameter read tool it also covers payment prerequisites, failure semantics, and invocation guidance. An agent has everything needed to decide to call it and to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3; the description nonetheless adds meaning by framing the comparison as an upgrade (from = current, to = target) and by spelling out all four parameters in the HTTP example, which disambiguates how name/from/to/ecosystem combine. It does not explain ecosystem options itself, relying on the schema for that.

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?

Opens with a specific verb and resource ('what changes between two releases of a package') and then enumerates exactly the diff surface: dependencies added/removed/re-ranged, licence change, deprecation, publish dates, intermediate releases, and OSV advisory status. The scope boundary 'registry metadata only: a source-code diff is not claimed' separates it cleanly from a code-diff or changelog tool in the same family.

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 'when' is implied by the purpose and the from->to upgrade framing, and it routes to get_example for calling syntax, but it never names alternatives such as deps_get_changes, deps_get_version_history, or deps_check_advisories to tell an agent which sibling to pick. No explicit when-not-to-use condition is given.

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