Store Canary

Sample a store's products

check_products

Read-onlyIdempotent

Read up to 10 published products from the public WooCommerce Store API and flag missing prices, missing images and out-of-stock items. Read-only: one run of GET requests only; never logs in, adds to cart or submits forms. Nothing is monitored or saved; ongoing checks are Store Canary Pro. A bare hostname is fine; URL paths are ignored and the host's homepage is checked.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	The store's public address, for example https://example.com. A bare hostname (example.com) is fine. Any path, query or fragment is ignored: the homepage of the host is checked.

Output Schema

Name	Required	Description
`url`	Yes	Normalized store origin that was checked.
`status`	Yes	checked = findings below; otherwise no store request was made.
`liteUrl`	Yes	Store Canary Lite on WordPress.org (free).
`overall`	Yes
`summary`	Yes
`auditUrl`	Yes	Full Store Canary audit (plain external link).
`findings`	Yes
`checkedAt`	Yes
`reportUrl`	No	Shareable read-only report page. The result is encoded in the link; nothing is stored.
`proTrialUrl`	Yes	Store Canary Pro 30-day free trial.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / url / description

Previous value: -"The store's public address, for example https://example.com"New value: +"The store's public address, for example https://example.com. A bare hostname (example.com) is fine. Any path, query or fragment is ignored: the homepage of the host is checked."

Changed1 schema field changedOct 30, 2026

addedOutput schema / properties / reportUrl

Added value: +{
+  "description": "Shareable read-only report page. The result is encoded in the link; nothing is stored.",
+  "format": "uri",
+  "type": "string"
+}

AddedOct 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: exactly one run of GET requests, no login, no cart, no form submission, and nothing monitored or saved. The 10-product cap and the persistence/auth boundaries are behavioral facts an agent could not derive from readOnlyHint/idempotentHint alone.

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?

Four front-loaded sentences: capability first, then safety boundary, then persistence limit, then URL handling. Efficient overall, though the URL sentence duplicates schema text and could be dropped without loss.

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 a rich annotation set, a fully documented single parameter and an output schema, the description supplies everything else an agent needs: what is sampled, what is flagged, what side effects do not occur, and what the URL input tolerates.

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?

Only one parameter, and its schema description already covers the bare-hostname acceptance and the path/query/fragment being ignored. The description's final sentence largely restates the schema rather than adding new semantics, so baseline 3 applies despite full coverage.

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 ('Read up to 10 published products from the public WooCommerce Store API') plus the exact findings it flags (missing prices, images, out-of-stock). The bounded sample of 10 products and the public Store API endpoint distinguish it from broader siblings like check_store.

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?

Gives a clear when-not ('ongoing checks are Store Canary Pro') and defines the read-only, one-shot scope, so an agent knows this is a single diagnostic run rather than monitoring. It does not explicitly route to or exclude sibling checks such as check_store or check_exposure, leaving some overlap for the agent to infer.

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

All Store Canary 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.