Sitejar Web Compliance Scanner

scan_website

Run a Sitejar compliance scan on ONE page: exactly the URL given, with no crawling and no link following. Returns a scan id, NOT a result: the scan is still running when this returns, so call get_scan_result afterwards and wait pollAfterSeconds between attempts. This tool cannot scan a whole site; full-site scans, which crawl every page and track a site over time, are started from the Sitejar dashboard. Each call spends one of the account's monthly single-page scans. Sitejar does not generate or apply any fix here, and makes no AI call: use get_fix_guidance for its own remediation guidance.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	The absolute URL of the single page to scan, for example https://example.com/pricing

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations supplied, the description carries the full disclosure burden and does so: the call is asynchronous ("the scan is still running when this returns"), consumes a metered resource ("one of the account's monthly single-page scans"), and makes no AI call or fix. The non-result return shape is stated outright, which is the single most important fact for avoiding misuse.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, all front-loaded: scope first, return shape second, cost third, capability limits last. No sentence repeats the name or the schema, and each one removes a distinct failure mode (crawling, treating the id as a result, unexpected billing, expecting an auto-fix).

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?

There is no output schema, so the description must explain what comes back — it does, naming the scan id and the follow-up tool plus the polling interval. For a one-parameter asynchronous scanner, nothing an agent needs to invoke and correctly chain it is missing.

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% for the single url parameter and the schema already gives an example. The description still adds real constraint beyond it by insisting on "exactly the URL given" with no link following, which prevents an agent from passing a homepage expecting a crawl. Baseline for a one-param tool is 4; the added scope constraint confirms it.

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 ("Run a Sitejar compliance scan") and pins the scope to "ONE page: exactly the URL given, with no crawling and no link following." It also explicitly separates itself from full-site scans (dashboard-only) and from get_scan_result, so an agent can distinguish it from every sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit call sequence: this returns a scan id, then "call get_scan_result afterwards and wait pollAfterSeconds between attempts." It also names the excluded case (whole-site scans, which must go to the dashboard) and routes remediation to get_fix_guidance, so both the when and the when-not are covered.

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

All Sitejar Web Compliance Scanner 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?