Outrings Web Intelligence

Compare a site against its last audit

what_changed

Re-audit a site and report what moved since it was last checked: which findings are new, which were resolved, and how each category score shifted. Use it after the user says they fixed something, or to verify that a deployment did not regress anything. Returns comparable=false when the site has no earlier snapshot, which is not an error: it means history starts now. Unlike the other tools this one WRITES: it stores a durable snapshot of the result, because a comparison against history requires contributing to it. The baseline is the most recent retained snapshot and snapshots are kept at most once per site per six hours, so baselineAt may not be the deployment immediately before this one: read baselineAt rather than assuming it is the last change. Check comparable before attributing any score movement to the site: when the ruleset differed between the two measurements it is false, and the difference then includes a change in grading rather than a change in the website.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	The website to inspect. A bare domain works: "example.com" is treated as https://example.com.

Output Schema

Name	Required	Description
`to`	No	One end of the comparison.
`from`	No	One end of the comparison.
`host`	Yes
`note`	No
`score`	No	Present instead of a diff when history starts with this call.
`summary`	No
`resolved`	No
`worsened`	No
`currentAt`	No
`direction`	No
`spanHours`	No
`baselineAt`	No	Timestamp of the snapshot being compared against. Snapshots are retained at most once per site per six hours, so this may not be the deployment immediately before the current one.
`categories`	No
`comparable`	Yes	False when the two measurements used different rulesets, or when no earlier snapshot exists. Check this before attributing any score movement to the website.
`scoreDelta`	No
`newProblems`	No
`schemaChanged`	No
`partlyImproved`	No
`rulesetChanged`	No	Null when one snapshot predates version tracking.
`comparabilityNote`	No	Plain-language account of whether the two ends can be compared.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / url / description

Previous value: -"The website to inspect. A bare domain works — \"example.com\" is treated as https://example.com."New value: +"The website to inspect. A bare domain works: \"example.com\" is treated as https://example.com."

Changed1 schema field changedAug 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "baselineAt": {
+      "description": "Timestamp of the snapshot being compared against. Snapshots are retained at most once per site per six hours, so this may not be the deployment immediately before the current one.",
+      "format": "date-time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "categories": {
+      "items": {
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "delta": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "from": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "note": {
+            "type": "string"
+          },
+          "to": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "comparabilityNote": {
+      "description": "Plain-language account of whether the two ends can be compared.",
+      "type": "string"
+    },
+    "comparable": {
+      "description": "False when the two measurements used different rulesets, or when no earlier snapshot exists. Check this before attributing any score movement to the website.",
+      "type": "boolean"
+    },
+    "currentAt": {
+      "format": "date-time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "direction": {
+      "enum": [
+        "improved",
+        "regressed",
+        "stable",
+        "not-comparable",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "from": {
+      "description": "One end of the comparison.",
+      "properties": {
+        "at": {
+          "format": "date-time",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "grade": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "score": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "versions": {
+          "description": "Ruleset that produced this measurement. Null for snapshots written before version tracking existed.",
+          "properties": {
+            "collector": {
+              "type": "string"
+            },
+            "ruleset": {
+              "type": "string"
+            },
+            "schema": {
+              "type": "string"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "host": {
+      "type": "string"
+    },
+    "newProblems": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "partlyImproved": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "resolved": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "was": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "rulesetChanged": {
+      "description": "Null when one snapshot predates version tracking.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "schemaChanged": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "score": {
+      "description": "Present instead of a diff when history starts with this call.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "scoreDelta": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "spanHours": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "summary": {
+      "type": "string"
+    },
+    "to": {
+      "description": "One end of the comparison.",
+      "properties": {
+        "at": {
+          "format": "date-time",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "grade": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "score": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "versions": {
+          "description": "Ruleset that produced this measurement. Null for snapshots written before version tracking existed.",
+          "properties": {
+            "collector": {
+              "type": "string"
+            },
+            "ruleset": {
+              "type": "string"
+            },
+            "schema": {
+              "type": "string"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "worsened": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "host",
+    "comparable"
+  ],
+  "type": "object"
+}

First observedAug 18, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: it writes a durable snapshot, uses the most recent retained snapshot as baseline, limits snapshots to once per site per six hours, and warns that baselineAt may not be the immediately preceding deployment. It also explains that comparable=false can mean no history or a changed ruleset, which is critical context for interpreting results.

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?

The description is front-loaded with purpose and usage, then moves into write behavior and baseline caveats. It is dense but every sentence carries relevant operational information, though some explanatory clauses could be tightened.

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?

Given the simple input schema, existing output schema, and annotations, the description is complete: it covers the write behavior, snapshot cadence, baseline semantics, and comparable interpretation. An agent has enough information to invoke it correctly and interpret the key edge case.

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?

There is only one parameter and the schema has 100% description coverage, including the bare-domain handling. The description does not add URL semantics beyond what the schema already 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: re-audit a site and report findings and category-score movement since the last check. It clearly distinguishes the tool from a sibling like compare_websites by emphasizing comparison against history rather than another site.

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?

It gives explicit trigger scenarios: after the user says they fixed something, or to verify a deployment did not regress. It also explains the comparable=false case, but it does not name a specific alternative such as audit_website for first-time audits or compare_websites for site-to-site comparison.

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

All Outrings Web Intelligence 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?