Skip to main content
Glama

Check a WooCommerce store

check_store
Read-onlyIdempotent

Check a public WooCommerce store from the outside: is it reachable, is HTTPS valid and are redirects sane, is WooCommerce detected, do /cart/ and /checkout/ load, and are payment markers visible on checkout. Read-only: GET requests only, never adds to cart, logs in or submits forms. Returns pass/warn/fail findings. Pass a bare hostname or 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_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe 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

NameRequiredDescriptionDefault
urlYesNormalized store origin that was checked.
statusYeschecked = findings below; otherwise no store request was made.
liteUrlYesStore Canary Lite on WordPress.org (free).
overallYes
summaryYes
findingsYes
checkedAtYes
reportUrlNoShareable read-only report page. The result is encoded in the link; nothing is stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / auditUrl
      Removed value: -{
      -  "description": "Full Store Canary audit (plain external link).",
      -  "format": "uri",
      -  "type": "string"
      -}
    • removedOutput schema / properties / proTrialUrl
      Removed value: -{
      -  "description": "Store Canary Pro 30-day free trial.",
      -  "format": "uri",
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "status",
      -  "url",
      -  "checkedAt",
      -  "overall",
      -  "summary",
      -  "findings",
      -  "auditUrl",
      -  "liteUrl",
      -  "proTrialUrl"
      -]New value: +[
      +  "status",
      +  "url",
      +  "checkedAt",
      +  "overall",
      +  "summary",
      +  "findings",
      +  "liteUrl"
      +]
  2. Changed1 schema field changed
    • 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."
  3. Changed1 schema field changed
    • 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"
      +}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the bar is lower, yet the description adds real behavioral detail: GET requests only, never adds to cart, logs in, or submits forms, and it returns pass/warn/fail findings. That is exactly the kind of side-effect and output-shape context annotations cannot convey.

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?

Front-loaded with purpose, then the read-only guarantee, then return shape, then input note — a sensible ordering with no filler. The final clause about paths being ignored duplicates the schema wording, a small redundancy that keeps it from a 5.

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?

An output schema exists, so return values need no elaboration, and the description still flags pass/warn/fail. With one fully documented parameter, explicit preconditions, and an explicit side-effect guarantee, an agent has everything needed to call this correctly.

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 single `url` parameter already documents bare-hostname acceptance and path/query/fragment being ignored. The description repeats the same facts rather than adding format, normalization, or failure-handling nuance, so 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?

Names a concrete verb and resource ('Check a public WooCommerce store from the outside') and enumerates exactly what is inspected: reachability, HTTPS validity, redirect sanity, WooCommerce detection, /cart/ and /checkout/ loading, and payment markers. That breadth also implicitly separates it from narrow siblings like check_ssl or check_speed.

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?

The framing 'from the outside' plus 'public' store establishes the precondition (no authenticated access) and the read-only intent, and the input guidance tells the agent a bare hostname is acceptable. It stops short of explicitly stating when to pick this bundled check over the narrower single-concern siblings, so it is clear context without exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.