Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_delete_tax_class

Destructive

Deletes a WooCommerce tax class. Ask the user for confirmation before calling with confirm=true. Mirrors woocommerce-mcp-server method delete_tax_class using local WordPress authentication; no WooCommerce REST API keys are required.

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_id": "<site_id>",
      "slug": "<slug>",
      "confirm": "<confirm>"
    },
    "name": "wc_delete_tax_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe tax class slug.
forceNoIf true, permanently delete where WooCommerce supports forced deletion.
confirmYesMust be true only after the user explicitly confirms this WooCommerce mutation.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds value beyond that by mandating a user-confirmation gate and by explaining the authentication path (local WordPress auth, no WooCommerce REST API keys required), which an agent cannot infer from structured fields.

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?

Three short sentences, front-loaded with the action and then the confirmation precondition. The trailing sentence on mirroring the woocommerce-mcp-server method is somewhat incidental but still carries authentication context that is not elsewhere available.

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 destructive mutation the description covers safety and auth, but it is silent on consequences: whether force is needed for permanent deletion, what happens to tax rates attached to the class, or what a failure looks like. With a fully documented schema and destructive annotations the gaps are tolerable but real.

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 coverage is 100%, so all four parameters including slug, force and confirm are documented in the schema itself. The description only reinforces the confirm's user-approval semantics and adds nothing about force or the site_id lookup, so it matches the baseline rather than exceeding it.

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 opens with a precise verb+resource ("Deletes a WooCommerce tax class"), which cleanly separates it from sibling rate tools like wc_delete_tax_rate by naming the resource type. It does not explicitly call out a sibling or scope boundary, so it stops short of a 5.

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?

The definition gives one concrete procedural rule: ask the user for confirmation before calling with confirm=true. That is real usage guidance, but it is about the confirmation step rather than when to choose this tool versus alternatives (e.g., deleting a tax rate instead of a class).

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

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources