Skip to main content
Glama

YRUZ Site Audit (0.01 USDC)

site_audit
Read-onlyIdempotent

Website audit in one call: TLS certificate, security headers, HTTPS redirect, HTTP/2 and HTTP/3, compression, response time, redirects, SEO tags and AI-agent readiness (llms.txt, robots rules for AI bots, sitemap, structured data). Scores 0-100 per area with concrete fixes. 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":"site_audit"}. Same tool over HTTP: https://yruz.one/api/audit?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": "site_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeswebsite URL or domain (required), e.g. https://example.com

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the bar is lower, yet the description adds genuinely non-obvious behavior: 0.01 USDC x402 payment with no account, invalid input refused before payment, failed runs never charged, and PaymentRequired returned without payment. It does not detail runtime limits or response shape, keeping it below a 5.

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 capability list, then pricing, then call mechanics — a sensible order, and the long enumerations earn their place by defining scope. The trailing raw HTTP endpoint URL is somewhat incidental bloat for an MCP tool, 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?

With no output schema, the description compensates by stating results are 0-100 scores per area with concrete fixes, and it covers pricing, error behavior, and how to obtain an example. It stops short of describing the report structure or expected latency, but an agent has enough to call it 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?

With a single parameter at 100% schema description coverage, the schema already carries the parameter meaning and the example value. The description adds only marginal semantics (invalid input is rejected before charge), so the baseline 3 is appropriate.

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?

Opens with a specific verb+resource ('Website audit in one call') then enumerates exactly what is audited (TLS, headers, redirects, HTTP/2-3, SEO, AI-agent readiness). This clearly separates it from narrower siblings like url_safety_check, uptime_check, broken_links, and domain_intel.

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 implied by the 'in one call' framing and the payment/how-to-call instructions, but there is no explicit routing guidance (e.g., 'use this instead of uptime_check when you want a full report' or when-not-to-use). The agent must infer when this is preferable to the many overlapping URL/domain siblings.

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.