Skip to main content
Glama
Sign In

Web Scan

by io.github.ankitkumarjha515
OverviewDiscussionsAdmin

Scan a URL

scan_url
Read-only

Run a fresh Web Scan audit of a public URL and return its score (0-100), grade, and every failing or warning check with its id, title and fix: the result is complete in itself. reportUrl is a shareable link only when the request carries a signed-in Web Scan token (reports are saved for signed-in users only); otherwise it is null and nothing is stored. fullReportUrl is always present: the full report on the website, to share with the user. Use this first, to find out what to fix on a live page. Takes about 5-15 seconds. Cannot scan localhost or private networks; use a deployed or preview URL.

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_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page to audit, e.g. "https://example.com/pricing" or a bare domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnly/openWorld annotations, the description discloses latency (~5-15 seconds), the conditional nature of reportUrl (shareable only with a signed-in token, null otherwise, nothing persisted), that fullReportUrl is always present, and the network restriction. That is exactly the behavioral context annotations cannot carry.

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?

Purpose and output are front-loaded, followed by the token/reportUrl caveat and timing. Dense and mostly waste-free, though the reportUrl versus fullReportUrl distinction is explained at slightly more length than the decision requires.

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 carries the full burden and does so: it enumerates returned fields, explains both URL variants, states the auth/persistence condition, gives timing, and lists the access restriction. An agent has everything needed 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the single url parameter is already documented with examples. The description still adds real constraint semantics — the target must be public, live, and not localhost or a private network — which sharpens how the agent should populate the field.

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 gives a specific verb and resource ("Run a fresh Web Scan audit of a public URL") plus the exact return shape (score 0-100, grade, failing/warning checks with id, title, fix). The word "fresh" and "Use this first" implicitly separate it from get_report (which fetches an existing report) and verify_fixes.

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?

"Use this first, to find out what to fix on a live page" states a clear triggering condition, and the closing sentence excludes localhost/private networks in favor of deployed or preview URLs. It stops short of explicitly naming which sibling to use instead when a report already exists or after fixes are applied, leaving that inference to the agent.

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

All Web Scan toolsInspect
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