Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Clear cart config

clear_cart_config
Destructive

Remove a workspace's cart configuration entirely, resetting it to never-configured; use force: true to clear it when orders or carts block removal.

Instructions

Remove the workspace's commerce settings entirely, putting the cart back to never-configured. A workspace with orders or carts is refused unless force: true is passed. To change individual settings rather than remove them, use update_cart_config.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clear_cart_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoClear even when the workspace has orders or carts. Without it, a workspace with either is refused and the error names which one is in the way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.73.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as destructive and not read-only, but the description adds important context: all commerce settings are removed and the cart returns to never-configured. It also discloses the guardrail that workspaces with orders or carts are refused without force, including that the error names the blocking object.

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 tight sentences, with the destructive outcome stated first and the alternative and force exception following. Every sentence adds useful routing or safety information.

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

Completeness5/5

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

For a one-parameter destructive reset tool, the description covers the outcome, refusal condition, force override, and alternative operation. No output schema exists, but the return behavior of interest here is the refusal/error naming, which is disclosed.

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 the schema already documents the force parameter and its effect in detail. The description reinforces force semantics and the refusal behavior, but adds little beyond what the schema already provides.

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 uses a specific verb and resource: it removes the workspace's commerce settings and resets the cart to never-configured. It also distinguishes the operation from update_cart_config by framing this tool as full removal rather than partial modification.

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

Usage Guidelines5/5

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

It states exactly when this tool applies, notes that a workspace with orders or carts is refused unless force is true, and explicitly points to update_cart_config for changing individual settings. The main alternative and the refusal condition are both covered.

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