mcp-server-woocommerce

create_tax_rate

Add a tax rate to WooCommerce by defining the applicable region (country, state, postcode), the rate percentage, and tax class.

Instructions

Create a tax rate. Set country/state/postcode for region, rate as percentage string (e.g. '18.0000'), and class for tax class.

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": {
      "rate": "<rate>",
      "name": "<name>"
    },
    "name": "create_tax_rate"
  }
}

Input Schema

Name	Required	Description	Default
`city`	No	City name
`name`	Yes	Tax rate name (e.g. 'GST 18%')
`rate`	Yes	Tax rate percentage (e.g. '18.0000')
`class`	No	Tax class slug	standard
`state`	No	State code (e.g. GJ, CA)
`fields`	No	Comma-separated fields to return in response
`country`	No	Country ISO 3166 code (e.g. IN, US)
`compound`	No	Whether this is a compound rate
`postcode`	No	Postcode or range (e.g. 396321)
`priority`	No	Tax rate priority
`shipping`	No	Whether rate applies to shipping

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Aug 6, 2026

TDQS

A3.6/5.0

Behavior2/5

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

Annotations only include openWorldHint=false, which pertains to schema strictness, not behavioral traits. The description carries the full burden for safety and side effects, but it only says 'Create a tax rate' without disclosing potential consequences like duplicate handling, permission requirements, or whether creation is reversible. This is a significant transparency gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, tightly written sentence that leads with the primary action and then covers the most salient parameters. There is no redundant phrasing or fluff; every word adds value.

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

Completeness2/5

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

The tool has 11 parameters and no output schema, yet the description only mentions a subset of parameters and omits the required 'name' field entirely. It also doesn't clarify what the response will look like or any edge cases. While the schema is rich, the description itself is incomplete for guiding an agent toward a successful invocation, especially given the missing required parameter.

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 parameters have individual descriptions. The tool description adds marginal value by grouping country/state/postcode as 'region' and giving an example for rate, but it doesn't go beyond what the schema already conveys. It also omits mention of the required 'name' parameter, which is present in the schema but not highlighted in the description.

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?

The description immediately states 'Create a tax rate' with a clear verb and resource, and then enumerates the key configuration elements (country/state/postcode, rate, class). This distinguishes it from sibling tools like update_tax_rate, delete_tax_rate, and get_tax_rate.

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?

The tool's purpose as a creation operation is clear, and the description gives practical guidance on what fields to set. It doesn't explicitly say 'use this instead of update_tax_rate', but the context and naming make the usage context unambiguous. No exclusions or alternative mentions are provided, so it misses a top score.

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

Deploy Server