Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ DependencyPulse Changes Since (0.008 USDC)

deps_get_changes
Read-onlyIdempotent

Everything that changed for a package since a date: releases published, deprecations and yanks among them, the current latest, advisories published or modified for the package, and attribute changes YRUZ observed between its snapshots. For maintainers, CI and agents re-checking a dependency. 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_get_changes"}. Same tool over HTTP: https://yruz.one/api/deps/changes?ecosystem=npm&name=axios&since=2026-01-01

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

Input Schema

NameRequiredDescriptionDefault
nameYespackage name (required)
sinceNodate YYYY-MM-DD (default 90 days ago)
ecosystemNonpm (default), pypi or composer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / ecosystem / examples
      Added value: +[
+  "npm"
+]
    • addedInput schema / properties / name / examples
      Added value: +[
+  "axios"
+]
    • addedInput schema / properties / since / examples
      Added value: +[
+  "2026-01-01"
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description goes far beyond standard annotations by disclosing crucial operational behavior, such as the exact cost per call, the failure conditions (invalid input refusal), and the error response (`x402 PaymentRequired`). This is critical behavioral data not provided in the hints.

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?

While quite lengthy, the description is well-structured and front-loads the most important information (what it does, audience, and cost). Every sentence contributes significantly to the overall understanding of the tool.

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?

Given the complexity of a paid, financial API, the definition is extremely complete. It covers the function, audience, payment process, error handling, and even provides a reference to the HTTP endpoint, leaving nothing for the agent to guess.

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?

Since the schema coverage is 100%, the baseline is strong. The description still adds value by clarifying the expected date format (YYYY-MM-DD) and listing available ecosystem options like 'pypi or composer,' adding helpful context to the structured data.

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 provides a highly specific breakdown of the tool's function, listing exactly what is tracked: releases, deprecations, yanks, advisories, and attribute changes. This highly detailed explanation clearly distinguishes it from other dependency checking siblings.

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

Usage Guidelines5/5

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

The tool specifies its intended audience (maintainers, CI, and agents), which guides usage. Furthermore, it includes critical usage guidelines regarding cost (0.008 USDC) and payment mechanism (x402), which dictates when and how to invoke the tool.

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