Skip to main content
Glama

YRUZ Broken Link Check (0.01 USDC)

broken_links
Read-onlyIdempotent

Find broken links on a web page: fetches the page, collects its links (internal and external) and checks up to 50 of them in parallel, reporting status code, redirect target and response time for each, with a summary of broken, redirected and healthy links. 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":"broken_links"}. Same tool over HTTP: https://yruz.one/api/links?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": "broken_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNolinks to check, 1-50 (default 30)
urlYespage URL (required)
scopeNoall (default) | internal | external

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/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it explains pricing, payment handling, refusal before payment on invalid input, no charge for failed runs, and the PaymentRequired response when unpaid. It also describes parallel checking and the reported fields, giving the agent a clear operational picture.

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 the core purpose and then covers payment, failure behavior, invocation, and HTTP access. It is somewhat dense and includes extra invocation details, but the information is useful and mostly earns its place.

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?

Given that there is no output schema, the description explains the returned status code, redirect target, response time, and summary categories. It also covers payment, error handling, and invocation, leaving little important context missing for a three-parameter read-only tool.

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?

The input schema already has 100% description coverage, so the baseline is 3. The description reinforces that links are checked up to 50 in parallel and mentions internal/external scope, but it does not add meaningful syntax or constraints beyond what the schema provides.

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 states a specific action and resource: it finds broken links on a web page by fetching the page, collecting internal and external links, and checking them. It is clear what the tool does, but it does not explicitly distinguish itself from nearby tools such as link_preview or site_audit.

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 implies when the tool is useful by describing a broken-link-checking workflow, and it explains payment and error behavior. However, it does not explicitly say when to use this instead of alternatives like link_preview, site_audit, or url_safety_check.

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.