Skip to main content
Glama

woo_helper_stripe_status

Retrieve read-only WooCommerce Stripe Gateway status for a site, including mode, enabled payment methods, express checkout, and Stripe.js loading per page.

Instructions

Read-only WooCommerce Stripe Gateway status from cvrt-woo-helper (recursively masked): mode, enabled methods, express checkout and Stripe.js loading per page.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.1/5.0
Behavior3/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. It does disclose two useful traits: that the operation is read-only and that output is 'recursively masked' (secrets are sanitized), which is real behavioral context. It does not address permissions/auth requirements, error conditions, or how the per-page breakdown is shaped, so it stops short of full transparency for an unannotated tool.

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?

One dense sentence that front-loads the action and scope with no filler. It is efficient but packs source, masking, and four output facets into a single colon-list, which is readable but slightly cramped.

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 usefully enumerates the returned fields, which compensates well for that gap. However, for a tool sitting among many Stripe/gateway siblings, the absence of any selection guidance or permission notes leaves the operational picture incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter 'site' and schema description coverage is 100%, so the schema fully documents it ('Site id (see list_sites)'). The description adds no meaning about the parameter beyond the schema; baseline for one param with complete schema coverage is 3, and nothing here earns above that — the 'per page' phrase refers to output, not the input.

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?

States a specific verb+resource: read-only WooCommerce Stripe Gateway status, and names the concrete fields returned (mode, enabled methods, express checkout, Stripe.js loading). It is clear what the tool does, though it does not explicitly distinguish itself from the similarly named sibling woo_helper_get_stripe.

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

Usage Guidelines3/5

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

Usage is only implied by 'Read-only ... status' plus the field list — an agent can infer this is a diagnostic read. There are no explicit when-to-use/when-not conditions and no routing to alternatives such as woo_helper_get_stripe or woo_helper_status.

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