Skip to main content
Glama

woo_helper_get_stripe

Retrieves Stripe express-checkout settings for a WooCommerce site, including enablement, button placements by page type, and checkout-only Stripe.js loading.

Instructions

The Stripe express-checkout settings cvrt-woo-helper manages: express checkout on/off, button locations per type and what they mean per page, and whether Stripe.js loads only on the checkout (scripts_checkout_only, so it does not load before consent on product pages).

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_get_stripe"
  }
}

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?

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It explains what the settings mean (including that scripts_checkout_only keeps Stripe.js off product pages before consent), which is genuinely useful context, but it never states that the call is read-only, requires authentication, or hits a live Stripe configuration rather than a cached copy.

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 sentence with no filler, but it is front-loaded with an abstract noun phrase ('The Stripe express-checkout settings cvrt-woo-helper manages') and packs explanatory clauses into a dense trailing list, which slows an agent's scan for the actual action.

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?

With no output schema, the description must convey what comes back; it does partly by enumerating the setting groups, but it omits the response shape and does not cover the required site parameter. Adequate but incomplete for a configuration-read tool.

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?

Only one parameter (site), fully documented in the schema at 100% coverage, so the baseline is 3. The description adds nothing about the site identifier or its relationship to list_sites, but there is little left for it to add.

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 names a specific resource (Stripe express-checkout settings) and enumerates the sub-settings, but never uses an explicit verb like 'get' or 'retrieve' for the tool itself — 'manages' describes the plugin, not the call. An agent can infer it reads settings, but it is not clearly distinguished from nearby siblings such as woo_helper_get_settings or woo_helper_stripe_status.

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 guidance about when to call this versus woo_helper_get_settings, woo_helper_stripe_status, or woo_helper_update_stripe. No prerequisites, no exclusions, and no mention of read-only usage context.

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