Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ RealityGraph Evidence (0.02 USDC)

reality_get_evidence
Read-onlyIdempotent

Evidence bundle for an entity: for each requested property (default: its core facts) every statement with rank, qualifiers and all its references (stated in, reference URL, title, publication and retrieval dates, archive URL), a reference-quality grade (sourced, wiki_imported, unsourced), and the Wikipedia articles linked to the entity. Reference URLs are as recorded by the source; they are not fetched live. Price: 0.02 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_get_evidence"}. Same tool over HTTP: https://yruz.one/api/reality/evidence?id=Q7624104&properties=P571%2CP159%2CP1128%2CP2139

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

Input Schema

NameRequiredDescriptionDefault
idYesWikidata id (required)
langNolanguage of labels, 2-3 letters (default en)
propertiesNoproperty ids, comma separated, up to 10 (default: core facts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / examples
      Added value: +[
+  "Q7624104"
+]
    • addedInput schema / properties / properties / examples
      Added value: +[
+  "P571,P159,P1128,P2139"
+]
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds substantial context beyond them: price (0.02 USDC via x402, no account or API key), the fact that invalid input is rejected before payment, failed runs are never charged, an unpaid call returns PaymentRequired, and that reference URLs are as recorded by the source rather than fetched live. The stale-data caveat is exactly the kind of trait an agent needs.

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 returned payload, then pricing/payment behavior, then a call example — a sensible order with little waste. The raw HTTP URL example is somewhat expendable, but every other sentence carries information an agent would otherwise have to guess.

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 carries the full burden of describing return values and does so in detail (statements, ranks, qualifiers, reference fields, quality grades, linked articles). Payment semantics and the pre-payment validation behavior are also covered, leaving no material gap for correct invocation.

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 id, lang and properties are already documented including defaults and the 10-property cap. The description only restates the default (core facts) and adds that each requested property yields statements plus references, which is marginal beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource — an evidence bundle for an entity, itemizing statements per property with rank, qualifiers, references, reference-quality grade and linked Wikipedia articles. This payload description effectively separates it from data-oriented siblings like reality_get_entity or reality_get_history, though no sibling is named explicitly.

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 only implied: the description explains the default (core facts) and how to invoke the tool, but never says when an agent should choose this over reality_get_entity, reality_get_conflicts or reality_get_history. There are no explicit exclusions or selection conditions.

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