Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ RealityGraph Entity Profile (0.004 USDC)

reality_get_entity
Read-onlyIdempotent

Normalized profile of one entity: label, description, aliases, types, official identifiers (LEI, ticker, VIAF, OpenCorporates, national registers ...), and the core facts for its kind (inception, country, headquarters, website, founders, CEO, employees and revenue over time, industry, population, licence, version ...). Every fact keeps rank, qualifiers (start, end, point in time), reference count and a status: observed, observed_unsourced, historical, deprecated or conflicting. Extra properties on request. Price: 0.004 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_entity"}. Same tool over HTTP: https://yruz.one/api/reality/entity?id=Q7624104

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reality_get_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoname instead of id (the top search hit is used and reported)
idNoWikidata id (required unless q), e.g. Q7624104
langNolanguage of labels, 2-3 letters (default en)
propertiesNoextra property ids, comma separated, up to 15, e.g. P1056,P2403

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / examples
      Added value: +[
+  "Q7624104"
+]
  2. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, and the description still adds substantial non-obvious context: 0.004 USDC per call, x402 payment on Base or Solana with no account/API key, invalid input refused before payment, failed runs never charged, and a PaymentRequired response without payment. That is exactly the behavioral disclosure an agent needs to decide whether and how to call it.

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 and returned fields are front-loaded, followed by pricing, error behavior, and call mechanics, so no sentence is wasted. The long parenthetical field enumerations ('inception, country, headquarters ... version ...') are verbose and trailing ellipses add little, costing it a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates well by describing return contents, per-fact rank/qualifiers/status values, and the payment failure mode. Minor gaps remain: no mention of response size, pagination, or rate limits for a potentially large profile.

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 description coverage is 100%, so the schema already documents q, id, lang, and properties (including the 15-property cap and format). The description adds nothing beyond a vague 'extra properties on request' that merely echoes the 'properties' parameter, so 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?

The description names a specific verb/resource pair ('Normalized profile of one entity') and enumerates the returned fields (aliases, identifiers, facts, statuses), so an agent can tell what it gets. It never names a sibling (reality_search, reality_resolve_entity, reality_compare) to distinguish lookups from searches or comparisons, so it falls short of a 5.

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: fetch this for a single known entity, use 'q' for a name lookup. It does not say when to prefer it over reality_search or reality_resolve_entity, nor what to do when an id is unknown. The prerequisite (payment via x402) and the get_example hint are stated, which keeps this above a 2.

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