DrUrls

free_page_check

Read-onlyIdempotent

Free single-page SEO/health audit of any public URL — no API key, no account. Returns the same score, grade, categories and issues as the product's free check, plus an upgrade field describing what the authenticated tools add. Rate limited per caller (3/day). Whole-site crawls, history and tasks need a DrUrls account.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	The page to audit, e.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond annotations: no API key or account required, a concrete rate limit (3/day per caller), and the exact return payload (score, grade, categories, issues, upgrade field) even though no output schema exists. It also explains the `upgrade` field's purpose, which is otherwise invisible.

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-loads the audit purpose, then limits, then return shape — dense but ordered. Slightly longer than necessary, with the rate-limit and account clauses partially overlapping.

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?

Despite having no output schema, the description explains return contents, the extra `upgrade` field, cost/auth model, and rate limits. An agent has everything needed to decide to call it and interpret the result.

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?

Single `url` parameter is fully documented in the schema (100% coverage) with an example, so the description adds nothing beyond 'any public URL'. Baseline 3 applies when the schema carries the parameter semantics.

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?

States a specific verb+resource+scope: single-page SEO/health audit of any public URL. It immediately distinguishes itself from the crawl/report siblings by saying whole-site crawls, history and tasks require an account.

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?

Explicitly frames this as the no-key, no-account path and names the boundary where siblings (start_scan, get_site_report, history) are needed. It doesn't name those siblings directly, so an agent must infer which authenticated tool to escalate to.

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

All DrUrls tools Inspect

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.