Skip to main content
Glama

woo_gateway_status

Check which WooCommerce payment gateways are available at checkout for a customer country, including Stripe express checkout status when the helper plugin is active.

Instructions

WooCommerce payment gateways for a customer country: id, title, enabled, available (offered at checkout, WooCommerce's own check for an empty cart, so minimum-total gateways show unavailable), plus cvrt-woo-helper's Stripe status (express checkout, where Stripe.js loads) when that plugin is active. cvrt-mcp-endpoints 1.17.0+.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
countryNoISO country code (default DE)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it explains that 'available' uses WooCommerce's empty-cart check, that minimum-total gateways may show unavailable, and that Stripe status is included only when the cvrt-woo-helper plugin is active. It does not state read-only safety or permission requirements, but the return behavior is unusually well disclosed for a status tool.

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?

The description is a single front-loaded sentence that avoids filler and puts the resource first. It is dense but every clause contributes useful meaning, though the run-on structure slightly reduces readability.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain returned values, and it does so by naming fields and clarifying conditional behaviors. It is nearly complete for a simple status getter, though it omits error handling and explicit safety context that annotations would normally provide.

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%, so the schema already documents 'site' and 'country' with defaults and formats. The description adds only the phrase 'for a customer country', which reinforces the country parameter's purpose but does not meaningfully extend the schema semantics.

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?

The description clearly identifies the resource as WooCommerce payment gateways scoped to a customer country and enumerates the returned fields. It is specific but does not explicitly differentiate this tool from related siblings such as 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?

The description gives context that the tool is for a customer country but offers no explicit when-to-use or when-not-to-use guidance. It does not explain how to choose between this tool and the related Stripe status or helper status tools.

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