Store Canary

Time a store's key pages

check_speed

Read-onlyIdempotent

Time one download each of a store's homepage, one product page and the cart from Cloudflare's network. One sample per page, not a lab test or an average. 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_speed"
  }
}

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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description earns credit for adding real context: it discloses that a run issues GET requests only, never logs in or submits forms, takes exactly one sample per page, and that nothing is monitored or persisted. It does not describe expected response shape or timeout behavior, but the output schema covers returns.

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?

Three sentences, each carrying information (scope, sampling caveat, read-only guarantees, URL handling), with the core purpose front-loaded. The final URL sentence duplicates the schema, which is the only wasted space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only check with a full output schema, the description covers the important unknowns: sampling methodology, network vantage point, side-effect guarantees, and persistence. Minor gaps like timeouts or approximate duration are not critical to correct invocation.

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 is 100%, and the schema description already states that a bare hostname is fine and that paths, queries and fragments are ignored. The description largely restates that, adding no new parameter semantics, so the baseline 3 applies.

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 names a specific action (time one download each) applied to concrete resources (homepage, product page, cart) from a named network (Cloudflare). It explicitly distinguishes itself from ongoing monitoring by naming Store Canary Pro, so an agent can tell it apart from siblings like check_store or check_ssl.

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 clear conditions: it is a one-shot timing sample, not a lab test or average, and continuous checks belong to a different product. What's missing is explicit routing against the concrete siblings (e.g. when to prefer check_store over check_speed), but the usage context is otherwise unambiguous.

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.