Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ RealityGraph Resolve (0.01 USDC)

reality_resolve_entity
Read-onlyIdempotent

Entity resolution for a company or organization: from a name plus optional website domain, country, LEI or type, the candidate Wikidata entities with a transparent score, a confidence band (deterministic, high, medium, low), the matching and conflicting attributes, why each matched, and which extra input would disambiguate. Identifier matches (LEI, official website) are deterministic; names only rank. Never merges entities. Price: 0.01 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_resolve_entity"}. Same tool over HTTP: https://yruz.one/api/reality/resolve?name=Stripe&domain=stripe.com&country=US

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

Input Schema

NameRequiredDescriptionDefault
leiNoLegal Entity Identifier, 20 characters
nameYesentity name (required), e.g. Stripe
typeNocompany, organization, place, software or person
domainNoofficial website domain, e.g. stripe.com
countryNocountry, ISO 2-letter code, e.g. US

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / country / examples
      Added value: +[
+  "US"
+]
    • addedInput schema / properties / domain / examples
      Added value: +[
+  "stripe.com"
+]
    • addedInput schema / properties / name / examples
      Added value: +[
+  "Stripe"
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds substantial non-obvious behavior beyond them: it never merges entities, invalid input is refused before payment, failed runs are never charged, and an unpaid call returns an x402 PaymentRequired. Payment mechanics (0.01 USDC on Base or Solana, no account/API key) are exactly the kind of context annotations cannot express.

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 purpose and outputs, then payment, then invocation hint — a sensible ordering. It is dense and the pricing/payment sentences are long, but nearly every clause carries information the agent needs (cost, refusal-before-charge, PaymentRequired behavior).

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 still enumerates the return payload (candidates, transparent score, confidence band, matching/conflicting attributes, match rationale, disambiguation hint). Combined with payment and refusal semantics, an agent has everything needed to call it and interpret the result.

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, but the description adds real semantic value: it explains that LEI and domain matches are deterministic while name alone only ranks, which tells the agent how to combine parameters for a confident result. It stops short of per-parameter syntax detail because the schema already supplies it.

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 ('Entity resolution for a company or organization') and immediately delimits the input set (name + optional domain/country/LEI/type). It is clearly distinguishable from siblings like reality_get_entity, reality_search and reality_compare, which do not perform candidate scoring/ranking.

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 description explains which inputs are deterministic (LEI, official website) versus ranking-only (names), which is useful selection guidance for inputs, and points to get_example for calling. However it never says when to prefer this over reality_search, reality_get_entity or reality_compare, so sibling routing is left to inference.

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