Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ RealityGraph Search (0.003 USDC)

reality_search
Read-onlyIdempotent

Find entities on Wikidata by name or alias, with an optional type filter (company, organization, place, software, person): id, label, description, types, the matched name, Wikipedia sitelink count as a notability signal, and links. The starting point for entity, evidence and resolve calls. Price: 0.003 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":"reality_search"}. Same tool over HTTP: https://yruz.one/api/reality/search?q=Stripe&type=company

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": {
      "q": "<q>"
    },
    "name": "reality_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesname to search (required), e.g. Stripe
langNolanguage of labels, 2-3 letters (default en)
typeNoany (default), company, organization, place, software or person
limitNoresults, 1-20 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / q / examples
      Added value: +[
+  "Stripe"
+]
    • addedInput schema / properties / type / examples
      Added value: +[
+  "company"
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Though annotations already declare readOnly/openWorld/idempotent, the description adds substantial behavior an agent cannot infer: x402 payment of 0.003 USDC on Base or Solana, no account or API key, invalid input refused before payment, failed runs never charged, and a PaymentRequired response without payment. This is exactly the payment/auth context that matters for an agent deciding whether to call.

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?

Purpose and return fields are front-loaded and the payment caveat is stated compactly. It is slightly padded by the redundant HTTP endpoint URL and the get_example hint, which are useful but not essential to tool selection.

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 fully enumerates the return shape (id, label, description, types, matched name, Wikipedia sitelink count, links) and covers cost, payment failure modes, and the entry point into the downstream reality_* chain. Nothing needed to invoke it correctly is missing.

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%, so all four parameters (q, lang, type, limit) are already documented in the schema. The description restates the type filter and its values, and shows a URL example using q and type, but adds no syntax or default detail for lang or limit. Baseline 3 is appropriate.

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?

States a specific verb and resource — 'Find entities on Wikidata by name or alias' — plus the optional type filter and the exact fields returned. This distinguishes it clearly from reality_get_entity and reality_resolve_entity, which operate on an already-identified entity.

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

Usage Guidelines4/5

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

'The starting point for entity, evidence and resolve calls' explicitly routes the agent to this tool before the downstream sibling calls. There are no explicit when-not conditions (e.g. use reality_resolve_entity when you have a URL or ID), so it falls short of a 5.

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