Go Voltic site scan

Scan a website

scan_site

Read-only

Score a public web page for structure and content, AI visibility, speed signals, accessibility basics and trust, and count how many of twenty-one published AI-agent standards it meets (robots.txt, sitemap, Link headers, DNS-AID, Markdown negotiation, Content Signals, Web Bot Auth, API catalog, MCP and A2A cards, agent skills, WebMCP, auth.md, OAuth discovery, and five machine payment protocols). Free: returns all category scores, the first three findings with fixes, and counts for the remainder. Takes 10 to 30 seconds.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http or https address, e.g. https://example.com. Private and local hosts are refused.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real value beyond them: a latency expectation (10-30 seconds) and the fact that free calls return truncated findings (all category scores, first three findings with fixes, counts for the rest). It does not explain what a paid/full call looks like or how failures are reported.

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 verb and the scored dimensions, then tacks cost and latency on at the end where they belong. The long parenthetical enumerating 21 standards is dense but earns its place by telling the agent the breadth of the check.

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 carries the job of explaining returns and does so at a summary level (category scores, findings with fixes, counts). A bit more on the shape of scores or how to obtain the remaining findings would make it fully sufficient.

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?

Only one parameter and the schema documents it at 100% coverage, including the private/local host restriction. The description adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 and resource ('Score a public web page') and enumerates the exact dimensions scored plus the 21-standard count, with the standards named. An agent knows precisely what this produces without opening anything else.

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: the tool operates on public http/https pages, private and local hosts are refused, and it takes 10-30 seconds. There is no explicit statement of when to reach for this versus other checks, though the free-tier limits of the response are spelled out, which helps an agent decide whether to call.

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

All Go Voltic site scan 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.

Resources

Need Help?