Store Canary

Check a store's SEO basics

check_seo_basics

Read-onlyIdempotent

Check a store's robots.txt (and whether it blocks the whole site), its XML sitemap, the homepage title and meta description, and noindex on the homepage. 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_seo_basics"
  }
}

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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds concrete behavioral facts the annotations cannot express: a single run of GET requests, no login, no cart addition, no form submission, and no persistence of results. It stops short of stating request volume or rate limiting, which is the remaining behavioral unknown for a crawler-style tool.

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 scope enumeration is front-loaded and every clause carries information about coverage or safety. The final sentence on hostname handling partially duplicates the schema description, which is the only wasted space.

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 one-parameter read-only checker with an output schema, the definition covers all an agent needs: what is checked, what is not done, that nothing persists, and how the input URL is normalized. Return-value interpretation is correctly left to the output 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?

There is a single parameter at 100% schema description coverage, so the schema already documents the format, maxLength, and path/query/fragment handling. The description's 'bare hostname is fine; URL paths are ignored' restates the schema rather than adding new semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and then enumerates exactly what is inspected: robots.txt (including whole-site blocking), the XML sitemap, homepage title and meta description, and homepage noindex. That enumerated scope clearly separates it in practice from check_speed, check_ssl, or check_policies, though no sibling tool is named explicitly.

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 draws a clear boundary against the paid alternative — 'Nothing is monitored or saved; ongoing checks are Store Canary Pro' — which tells the agent when this tool is the wrong choice. It does not, however, state when to prefer this over a broader sibling like check_store or check_exposure for a first-pass audit.

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.