Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ DependencyPulse Advisory (0.002 USDC)

deps_get_advisory
Read-onlyIdempotent

One advisory from OSV by its id or alias (GHSA-..., CVE-..., PYSEC-..., RUSTSEC-...): summary, details, severity (CVSS vectors), aliases, published and modified dates, withdrawn flag, every affected package with its ranges and fixed versions as published, and references. Price: 0.002 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_advisory"}. Same tool over HTTP: https://yruz.one/api/deps/advisory?id=GHSA-35jh-r3h4-6jhm

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": "deps_get_advisory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesadvisory id (required), e.g. GHSA-29mw-wpgm-hmr9 or CVE-2021-23337

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / examples
      Added value: +[
+  "GHSA-35jh-r3h4-6jhm"
+]
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond annotations, it discloses pricing (0.002 USDC), payment mechanics via x402, supported chains, no account/API key requirement, invalid-input refund behavior, failed-run non-charge behavior, and the PaymentRequired response when unpaid. These are highly relevant operational details that annotations alone do not provide.

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 purpose is front-loaded and the description avoids filler. It is dense because it includes return contents, payment rules, invocation guidance, and an HTTP endpoint, but nearly all of that information is useful for this paid 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?

There is no output schema, but the description enumerates the advisory fields returned and explains payment and error behavior. Given the single required parameter and read-only annotations, this is complete enough for correct invocation.

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 description coverage is 100% for the single id parameter, so the baseline is 3. The description adds value by clarifying that the id may be an alias and by listing accepted identifier families such as GHSA, CVE, PYSEC, and RUSTSEC.

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 a specific verb and resource: retrieving one OSV advisory by id or alias. It also enumerates the returned fields, making the tool's purpose unambiguous, though it does not explicitly name or contrast sibling tools such as deps_check_advisories or deps_get_package.

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?

Usage is implied by the phrase 'by its id or alias' and the listed id formats, and the description explains how to call the tool. However, it does not explicitly say when to use this tool versus alternatives like deps_check_advisories, deps_batch_check, or deps_get_package.

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