AgentReady Woo

scan_woo_store_readiness

Read-only

Use ONLY for a general storefront audit, readiness score, or fix recommendations. Do NOT use it to inspect a specific update or release; use preflight_woo_store for that. Check whether a public WooCommerce storefront is readable by shopping agents. Provide the store's HTTPS origin. The tool reads only public pages and the public WooCommerce Store API, changes nothing, and returns aggregate checks and recommendations without product text or customer data. When the storefront cannot be read at all, the tool abstains: state is UNREADABLE, score and grade are null, and the caller must not present that as a finding about the store.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`demo`	No	Run a deterministic synthetic demonstration instead of scanning a live store.
`store_url`	No	Public HTTPS origin of the WooCommerce storefront, for example https://shop.example.com

Output Schema

TableJSON Schema

Name	Required	Description
`grade`	Yes
`score`	Yes
`state`	Yes	UNREADABLE is an abstention, not a verdict about the store.
`checks`	Yes
`billable`	Yes
`scanned_at`	Yes
`unreadable`	Yes	Why nothing could be read. Null when the scan produced a score.
`evidence_status`	Yes
`recommendations`	Yes
`product_count_sampled`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "billable": {
+      "const": false
+    },
+    "checks": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "ok": {
+            "type": "boolean"
+          },
+          "weight": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "label",
+          "ok",
+          "weight"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "evidence_status": {
+      "enum": [
+        "LIVE_PUBLIC_SCAN",
+        "SYNTHETIC_DEMO"
+      ],
+      "type": "string"
+    },
+    "grade": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "product_count_sampled": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "recommendations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "scanned_at": {
+      "type": "integer"
+    },
+    "score": {
+      "maximum": 100,
+      "minimum": 0,
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "state": {
+      "description": "UNREADABLE is an abstention, not a verdict about the store.",
+      "enum": [
+        "SCORED",
+        "UNREADABLE"
+      ],
+      "type": "string"
+    },
+    "unreadable": {
+      "additionalProperties": false,
+      "description": "Why nothing could be read. Null when the scan produced a score.",
+      "properties": {
+        "detail": {
+          "type": "string"
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "reason",
+        "detail"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "state",
+    "score",
+    "grade",
+    "unreadable",
+    "checks",
+    "product_count_sampled",
+    "recommendations",
+    "scanned_at",
+    "billable",
+    "evidence_status"
+  ],
+  "type": "object"
+}

AddedSep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations, the description discloses that it reads only public pages, returns aggregate checks/recommendations without product text or customer data, and abstains with null score/grade when the store is unreadable. This clarifies non-obvious behavior.

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 front-loaded with the exact use case and exclusion, followed by essential behavioral details accordingly. Every sentence adds decision-relevant info without redundancy.

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?

Complete enough: it distinguishes from sibling preflight_woo_store, clarifies read-only scope, return nature, and unreadable handling, while params are fully covered by an explicit schema.

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 description coverage is 100% and both parameters (store_url and demo) are clearly described in the schema. The description reinforces that the store URL should be an HTTPS origin but does not add significant new parameter semantics beyond the schema.

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 ('audit/readiness/fix recommendations' for a WooCommerce storefront) and explicitly differentiates itself from the sibling preflight_woo_store, telling the agent exactly what it is for and what it is not for.

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?

Explicitly states when to use the tool (general audit, readiness score, fix recommendations), when NOT to use it (specific update/release verification), and names the alternative tool (preflight_woo_store). It also specifies the required input type (public HTTPS origin).

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

All AgentReady Woo 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.