Skip to main content
Glama

YRUZ Link Unfurl (0.003 USDC)

link_preview
Read-onlyIdempotent

Link preview of any URL in one call: title, description, site name, canonical URL, Open Graph and Twitter card fields, preview image, favicon, theme color, oEmbed endpoint and JSON-LD types. Use it to render rich links or to check how a page will look when shared. 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":"link_preview"}. Same tool over HTTP: https://yruz.one/api/unfurl?url=https%3A%2F%2Fyruz.one%2F

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": {
      "url": "<url>"
    },
    "name": "link_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespage URL (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url / examples
      Added value: +[
      +  "https://yruz.one/"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses payment behavior in detail: 0.003 USDC via x402, invalid input refused before payment, failed runs never charged, and PaymentRequired returned without payment. It also notes read-only/open-world behavior implicitly through the pricing and no-account model, adding substantial operational context.

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 description is front-loaded with purpose and return fields, followed by usage, pricing, and invocation details. It is somewhat dense but each section carries useful information; no sentence is clearly wasted.

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 compensates by listing the returned metadata fields. It also covers payment requirements and failure behavior, making it complete enough for an agent to call the tool correctly.

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% and the single required url parameter is already well documented in the schema. The description's phrase 'any URL' adds only marginal meaning beyond the schema's example and description.

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?

The description states a specific verb and resource: it produces a link preview for any URL and enumerates the metadata fields returned. This clearly distinguishes it from siblings like web_extract or url_safety_check, which serve different purposes.

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?

It gives clear usage contexts: render rich links or check how a page will look when shared. It does not explicitly name alternatives or when not to use it, but the intended use cases are unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.