Skip to main content
Glama

woo_helper_send_test_email

Send a real WooCommerce order-email preview to a recipient with temporary, unsaved settings so you can check the design before saving it.

Instructions

SENDS A REAL EMAIL: a WooCommerce order-email preview to to. settings (same keys as woo_helper_update_emails) are applied to this one email only and NOT saved, to try a look before saving it. Rate limited (30 s per user, 10 per hour per site; 429). Needs WooCommerce 9.6+ (409) and cvrt-woo-helper 0.2.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>",
      "to": "<to>"
    },
    "name": "woo_helper_send_test_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient address
siteYesSite id (see list_sites)
settingsNoUnsaved overrides for this test email

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it warns the operation sends a real email (side effect), that settings are not persisted, that rate limits apply (30 s per user, 10/hour per site) with 429, and that WooCommerce 9.6+ / cvrt-woo-helper 0.2.0+ are required with 409. These are exactly the operational facts an agent cannot get from the schema, including the one artifact of the description being additive rather than redundant. The only minor omission is the success response format.

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?

Extremely dense but front-loaded: the consequential fact ("SENDS A REAL EMAIL") comes first and every clause carries information (non-persistence, limits, version floors, error codes). The telegraphic parenthetical style is efficient but slightly reduces readability for an agent parsing prose.

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?

For a 3-parameter mutation-adjacent tool with no output schema and no annotations, the definition covers side effects, persistence semantics, limits and failure codes, which is nearly everything needed to call it safely. It leaves the return payload and the behavior when `settings` is omitted implicit, a small residual gap.

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

Parameters4/5

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

Schema coverage is 100% and the nested settings object is documented inline, so the baseline is 3. The description earns a point above baseline by explaining that `settings` uses the same keys as woo_helper_update_emails and is applied non-persistently, which the schema alone does not convey.

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?

Names a specific verb and resource ("SENDS A REAL EMAIL ... order-email preview to `to`") and immediately distinguishes it from the sibling that persists settings by noting these overrides are "applied to this one email only and NOT saved." An agent can tell this apart from woo_helper_update_emails without opening either schema.

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

Usage Guidelines4/5

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

Gives a clear use context — "to try a look before saving it" — which positions this as a pre-save preview step relative to woo_helper_update_emails. It stops short of an explicit "use update_emails to persist" instruction or a stated when-not-to-use case, so it is strong but not a full routing rule.

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