Skip to main content
Glama
Sign In

WhizzyCommerce

by com.whizzycommerce
OverviewDiscussionsAdmin

settings_catalogue_mode

Show the products without selling them. 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
catalogueModeYestrue: the shop shows its products and prices and sells nothing; every buy button and the basket are hidden. Pro only. false: it sells again.
catalogueHidePricesNoIn catalogue mode, hide the prices as well, for a shop that quotes. Off by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / catalogueHidePrices
      Added value: +{
+  "description": "In catalogue mode, hide the prices as well, for a shop that quotes. Off by default.",
+  "type": "boolean"
+}
  2. Added

TDQS

B3/5.0
Behavior1/5

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

The description says 'Calling this changes nothing,' but the annotations declare readOnlyHint=false, creating a direct conflict about whether the tool modifies state. Although the description usefully explains the preview and confirmation-link behavior, that contradiction undermines its transparency about the tool's side effects.

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

Conciseness3/5

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

The purpose is front-loaded, and the preview/confirmation behavior is explained clearly. However, the sentence 'Money is integer minor units (cents)' does not apply to this tool's boolean-only parameters and does not earn its place.

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 simple two-boolean settings tool with full schema coverage and no output schema, the description provides enough context about the preview and merchant-only confirmation flow. It omits the Pro-only constraint, but the schema already captures that detail.

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 both boolean parameters are already well documented in the schema. The description adds no additional parameter-level meaning and includes an irrelevant sentence about money being in minor units despite there being no monetary parameters.

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 clear outcome: showing products without selling them. It does not explicitly name 'catalogue mode' as the setting being changed, but the name and schema make the intended effect recognizable. It also does not distinguish this from sibling settings tools beyond the implied outcome.

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 description implies the use case (display products without enabling sales) and adds the constraint that only the merchant can confirm the change on the generated page. It does not explicitly say when to use this versus related settings tools, nor does it state exclusions or alternatives.

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