Skip to main content
Glama

preflight_woo_store

Read-only

Use ONLY before a specific WooCommerce update or release when you need protocol-family evidence. Do NOT use it for a general score or fix list; use scan_woo_store_readiness for that. Inspect selected public WooCommerce and agent-protocol surfaces and return per-family PASS, FAIL, BLOCKED or UNMEASURED evidence. It changes nothing, is free, and BLOCKED or UNMEASURED is an abstention rather than a finding about the store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_originYesPublic HTTPS origin of the WooCommerce store, with no path, query, credentials, private host, or customer data; for example https://shop.example.com.
requested_familiesNoPublic protocol families to inspect. Omit to check all supported families; use only woo, robots, jsonld, mcp, ucp, or acp.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
stateYes
checksYes
unknownsYes
observed_atYes
sample_seedYes
sample_sizeYes
store_originYes
catalogue_totalYes
protocol_bundlesYes
requested_familiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / requested_families / description
      Added value: +"Public protocol families to inspect. Omit to check all supported families; use only woo, robots, jsonld, mcp, ucp, or acp."
    • addedInput schema / properties / store_origin / description
      Added value: +"Public HTTPS origin of the WooCommerce store, with no path, query, credentials, private host, or customer data; for example https://shop.example.com."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "catalogue_total": {
      +      "minimum": 0,
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "checks": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "evidence": {
      +            "type": "object"
      +          },
      +          "family": {
      +            "enum": [
      +              "woo",
      +              "robots",
      +              "jsonld",
      +              "mcp",
      +              "ucp",
      +              "acp"
      +            ],
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "reasonCode": {
      +            "enum": [
      +              "TARGET_INVALID",
      +              "TARGET_PRIVATE",
      +              "TARGET_REDIRECT_UNSAFE",
      +              "TARGET_DNS_REBIND",
      +              "TARGET_TIMEOUT",
      +              "TARGET_BYTES_EXCEEDED",
      +              "TARGET_RATE_LIMITED",
      +              "ROBOTS_BLOCKED",
      +              "WOO_API_UNAVAILABLE",
      +              "WOO_SAMPLE_EMPTY",
      +              "JSONLD_PRODUCT_MISSING",
      +              "JSONLD_OFFER_MISSING",
      +              "DISCOVERY_UNDECLARED",
      +              "PROTOCOL_VERSION_UNSUPPORTED",
      +              "PROTOCOL_SCHEMA_INVALID",
      +              "MCP_INITIALIZE_FAILED",
      +              "MCP_TOOLS_LIST_FAILED",
      +              "MCP_TOOL_ANNOTATION_UNSAFE",
      +              "MCP_TOOL_CALL_FAILED",
      +              "UCP_PROFILE_INVALID",
      +              "ACP_PROFILE_INVALID",
      +              "CROSS_SURFACE_CONFLICT",
      +              "OWNERSHIP_REQUIRED",
      +              "OWNERSHIP_EXPIRED",
      +              "ACTIVE_FLOW_FORBIDDEN",
      +              "EVIDENCE_INVALID",
      +              "INFRA_PERSISTENCE_FAILED",
      +              "UNMEASURED_SOURCE",
      +              "CONNECTION_UNVERIFIABLE",
      +              "INVALID_MIME",
      +              "INVALID_JSON",
      +              "PAGINATION_DRIFT",
      +              "CANCELED_BY_CALLER"
      +            ],
      +            "type": "string"
      +          },
      +          "state": {
      +            "enum": [
      +              "PASS",
      +              "FAIL",
      +              "BLOCKED",
      +              "NOT_APPLICABLE",
      +              "UNMEASURED"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "family",
      +          "state",
      +          "evidence"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "kind": {
      +      "const": "preflight"
      +    },
      +    "observed_at": {
      +      "format": "date-time",
      +      "type": "string"
      +    },
      +    "protocol_bundles": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "requested_families": {
      +      "items": {
      +        "enum": [
      +          "woo",
      +          "robots",
      +          "jsonld",
      +          "mcp",
      +          "ucp",
      +          "acp"
      +        ],
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "sample_seed": {
      +      "type": "string"
      +    },
      +    "sample_size": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "state": {
      +      "enum": [
      +        "ACCEPTED",
      +        "REJECTED",
      +        "PARTIAL",
      +        "BLOCKED",
      +        "UNMEASURED"
      +      ],
      +      "type": "string"
      +    },
      +    "store_origin": {
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "unknowns": {
      +      "items": {
      +        "enum": [
      +          "TARGET_INVALID",
      +          "TARGET_PRIVATE",
      +          "TARGET_REDIRECT_UNSAFE",
      +          "TARGET_DNS_REBIND",
      +          "TARGET_TIMEOUT",
      +          "TARGET_BYTES_EXCEEDED",
      +          "TARGET_RATE_LIMITED",
      +          "ROBOTS_BLOCKED",
      +          "WOO_API_UNAVAILABLE",
      +          "WOO_SAMPLE_EMPTY",
      +          "JSONLD_PRODUCT_MISSING",
      +          "JSONLD_OFFER_MISSING",
      +          "DISCOVERY_UNDECLARED",
      +          "PROTOCOL_VERSION_UNSUPPORTED",
      +          "PROTOCOL_SCHEMA_INVALID",
      +          "MCP_INITIALIZE_FAILED",
      +          "MCP_TOOLS_LIST_FAILED",
      +          "MCP_TOOL_ANNOTATION_UNSAFE",
      +          "MCP_TOOL_CALL_FAILED",
      +          "UCP_PROFILE_INVALID",
      +          "ACP_PROFILE_INVALID",
      +          "CROSS_SURFACE_CONFLICT",
      +          "OWNERSHIP_REQUIRED",
      +          "OWNERSHIP_EXPIRED",
      +          "ACTIVE_FLOW_FORBIDDEN",
      +          "EVIDENCE_INVALID",
      +          "INFRA_PERSISTENCE_FAILED",
      +          "UNMEASURED_SOURCE",
      +          "CONNECTION_UNVERIFIABLE",
      +          "INVALID_MIME",
      +          "INVALID_JSON",
      +          "PAGINATION_DRIFT",
      +          "CANCELED_BY_CALLER"
      +        ],
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "kind",
      +    "state",
      +    "store_origin",
      +    "requested_families",
      +    "sample_seed",
      +    "sample_size",
      +    "catalogue_total",
      +    "checks",
      +    "protocol_bundles",
      +    "observed_at",
      +    "unknowns"
      +  ],
      +  "type": "object"
      +}
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description adds meaningful behavioral context beyond the annotations: it states the tool 'changes nothing', is free, and that BLOCKED or UNMEASURED is an abstention rather than a finding. This explains result semantics and side-effect profile, which annotations alone (readOnlyHint, openWorldHint, destructiveHint) do not cover. It reinforces the read-only nature and clarifies how to interpret outcomes.

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?

Three sentences, all information-dense and front-loaded. The primary usage constraint is stated first, the exclusion and alternative second, and the behavioral/result semantics third. No filler or redundant content.

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?

Given the tool's moderate complexity (2 params, output schema present), the description covers usage context, scope, result interpretation, side-effects, and the alternative tool. It is complete for an agent to decide when to call it and what to expect.

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%, so both parameters (store_origin and requested_families) are already documented in the schema. The description references 'selected public surfaces' but does not add syntax or format details beyond the schema's own descriptions. With full schema coverage, the baseline of 3 is appropriate; the description provides marginal added meaning.

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 clearly states the tool inspects public WooCommerce and agent-protocol surfaces and returns per-family evidence (PASS, FAIL, BLOCKED, UNMEASURED). It explicitly distinguishes itself from scan_woo_store_readiness by naming it as the alternative for general scores or fix lists, so an agent can tell them apart without opening schemas.

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?

It gives explicit when-to-use guidance ('Use ONLY before a specific WooCommerce update or release when you need protocol-family evidence') and when-not-to ('Do NOT use it for a general score or fix list'), naming the sibling tool to use instead. No inference is needed.

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.