site-audit

audit_website_preview

Read-onlyIdempotent

FREE PREVIEW (1 audit per day per caller IP) of Santos Website Intelligence. Runs a fast Quick Intelligence Audit of one public page: fetch timing, page weight, SEO, basic HTML accessibility, security headers, Website Intelligence dimensions, pass/fail checks, and remediation guidance. It audits one page only—no crawling, JavaScript rendering, Core Web Vitals, WCAG certification, or vulnerability scanning. Note for hosted agents: the quota is keyed on the calling IP, so all users of one platform share a single daily preview. Treat it as a sample of the output, not as capacity. For real use, call the machine-payable production endpoint: GET https://api.santosautomation.com/api/audit?url=... — $0.015 USDC per successful audit on Base mainnet (eip155:8453) via x402 v2; no account or API key required.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	A publicly reachable HTTP or HTTPS page.

Output Schema

Name	Required	Description
`url`	Yes
`checks`	No	Individual pass/fail checks with detail.
`issues`	Yes
`scores`	Yes	performance, seo, accessibility, security (0-100 each).
`timing_ms`	No
`audited_by`	No
`fetched_at`	No
`http_status`	No
`overall_score`	Yes
`schema_version`	Yes
`website_intelligence`	No	Discoverable, Understandable, Callable, Trustworthy.
`website_intelligence_score`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 31, 2026

removedInput schema / properties / token

Removed value: -{
-  "description": "Optional verified-email token. Without it the daily free quota is keyed on the caller IP, which every caller behind that address shares — hosted agents should pass a token so each user gets their own allowance. Obtain one via POST /api/leads/verify/request then /confirm; valid 30 days.",
-  "type": "string"
-}

Changed1 schema field changedJul 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "audited_by": {
+      "type": "string"
+    },
+    "checks": {
+      "description": "Individual pass/fail checks with detail.",
+      "type": "object"
+    },
+    "fetched_at": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "http_status": {
+      "type": "integer"
+    },
+    "issues": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "overall_score": {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "schema_version": {
+      "type": "string"
+    },
+    "scores": {
+      "description": "performance, seo, accessibility, security (0-100 each).",
+      "type": "object"
+    },
+    "timing_ms": {
+      "type": "object"
+    },
+    "url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "website_intelligence": {
+      "description": "Discoverable, Understandable, Callable, Trustworthy.",
+      "type": "object"
+    },
+    "website_intelligence_score": {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "schema_version",
+    "url",
+    "overall_score",
+    "scores",
+    "website_intelligence_score",
+    "issues"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 28, 2026

addedInput schema / properties / token

Added value: +{
+  "description": "Optional verified-email token. Without it the daily free quota is keyed on the caller IP, which every caller behind that address shares — hosted agents should pass a token so each user gets their own allowance. Obtain one via POST /api/leads/verify/request then /confirm; valid 30 days.",
+  "type": "string"
+}

First observedJul 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses critical behavioral traits: the one-per-day quota keyed to caller IP, the shared quota across hosted agent users, the non-crawling/non-rendering limitation, and the paid production alternative. This is substantial transparency about rate limits and operational constraints.

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?

The description is dense but every sentence earns its place: quota, scope, exclusions, hosted-agent warning, and production alternative. Key limitations are front-loaded, and the text remains structured and readable despite covering a lot of constraint information.

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?

For a single-parameter tool with a rich output schema and annotations, the description covers all essential context: what the tool examines, what it explicitly does not do, quota behavior, and how to transition to the production endpoint. Nothing an agent needs to decide whether to invoke it is missing.

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?

Schema coverage for the single `url` parameter is 100%, so the schema already documents it as a publicly reachable HTTP or HTTPS page. The description's phrase 'one public page' reinforces the parameter but adds little new semantic meaning beyond what the schema provides, so the baseline of 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?

The description states a specific verb and resource: it 'Runs a fast Quick Intelligence Audit of one public page' and enumerates exactly what it checks (fetch timing, page weight, SEO, security headers, etc.). It also clearly distinguishes itself from a production audit and from sibling tools by saying it is a single-page preview with no crawling or JavaScript rendering.

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?

The description explicitly says when to use this tool—for a free daily sample audit—and when not to use it: 'For real use, call the machine-payable production endpoint.' It also states the quota model and that it audits only one page, giving the agent clear conditions for selection.

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

All site-audit 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?