Skip to main content
Glama

woo_helper_status

Retrieve CVRT WooCommerce helper status: plugin version, WooCommerce and Stripe Gateway activation and versions, hub state, and GitHub token status for a specified site.

Instructions

cvrt-woo-helper status: plugin version, WooCommerce and Stripe Gateway active/version, whether the CVRT hub is on, GitHub token { set }.

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": {
      "site": "<site>"
    },
    "name": "woo_helper_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden: it does hint that the GitHub token is reported only as { set } rather than exposed, which is useful. But it never states that this is a read-only, non-mutating diagnostic, whether it triggers network/API calls, or whether it requires credentials.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact fragment with no filler, but the telegraphic style ('GitHub token { set }') and missing verb reduce readability compared with a plain sentence.

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

Completeness3/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 status tool with no output schema, listing the reported fields serves as a rough return-value preview, which is adequate. It still omits read-only semantics and how it differs from the overlapping status siblings.

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 description coverage is 100% and the single `site` parameter is documented in the schema as a site id referencing list_sites. The description adds no additional meaning about the site parameter, so baseline 3 applies.

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

Purpose3/5

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

The description enumerates what the status report contains (plugin version, WooCommerce/Stripe Gateway active+version, CVRT hub on/off, GitHub token set), which makes the resource clear, but it is phrased as a noun-list with no verb and gives no signal for distinguishing it from close siblings such as woo_helper_stripe_status, woo_gateway_status, or woo_helper_get_settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of the obvious overlapping siblings. An agent must guess whether to call this or woo_helper_stripe_status for Stripe-related checks.

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

Deploy Server

Other Tools