Skip to main content
Glama
Sign In

WhizzyCommerce

by com.whizzycommerce
OverviewDiscussionsAdmin

settings_tax

Set the shop's tax line. Money is integer minor units (cents). Calling this changes nothing: it returns a preview of what would change and a confirmation link. Only the merchant, on that page, can make it happen.

Input Schema

NameRequiredDescriptionDefault
taxRateBpsNoThe default tax rate in basis points: 23% is 2300, 0 switches tax off. Never 0 only to hide the tax line from shoppers: that stops charging VAT the shop may owe; showTaxLine is for that.
showTaxLineNofalse hides the "includes tax" line at checkout, in the cart, on order pages and receipts, for prices that include tax; the tax is still charged and on the invoice. Tax added on top always shows. What a merchant who asks to hide taxes or fees at checkout almost always wants.
taxIncludedInPriceNoWhether shelf prices already include tax (true, the EU way) or it is added at checkout.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / showTaxLine
      Added value: +{
+  "description": "false hides the \"includes tax\" line at checkout, in the cart, on order pages and receipts, for prices that include tax; the tax is still charged and on the invoice. Tax added on top always shows. What a merchant who asks to hide taxes or fees at checkout almost always wants.",
+  "type": "boolean"
+}
    • changedInput schema / properties / taxRateBps / description
      Previous value: -"The default tax rate in basis points: 23% is 2300, 0 switches tax off."New value: +"The default tax rate in basis points: 23% is 2300, 0 switches tax off. Never 0 only to hide the tax line from shoppers: that stops charging VAT the shop may owe; showTaxLine is for that."
  2. First observed

TDQS

B3.2/5.0
Behavior1/5

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

The description says 'Calling this changes nothing' and returns only a preview/confirmation link, while annotations declare readOnlyHint=false. That is a direct conflict about whether the call can modify state, so despite useful workflow detail the score is capped at 1 and flagged.

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?

Three short sentences, front-loaded with the core action and immediately followed by the two critical behavioral caveats. No filler; every sentence carries information.

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 zero-required-parameter, fully documented schema with no output schema, the description supplies the important workflow context: it returns a preview and confirmation link and requires merchant action. The remaining gap is sibling/alternative context, so it is not quite complete.

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%, including detailed semantics for taxRateBps and showTaxLine, so the schema already carries the parameter burden. The description adds only a generic 'integer minor units (cents)' note, which does not materially extend those parameter definitions.

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 states a specific verb and resource ('Set the shop's tax line') and clarifies that the call is a preview rather than the final write. It does not, however, distinguish this from the sibling settings_tax_rates tool or explain which tax-related setting belongs where.

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?

It explains the confirmation workflow and that only the merchant can complete the change, which implies when the tool is appropriate. It gives no explicit guidance on when to choose this over settings_tax_rates or other settings tools, and no exclusions.

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

All WhizzyCommerce 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