Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Suspend customer

suspend_customer
Destructive

Blocks a customer's sign-in and ends all active sessions while preserving orders and carts. Refuses accounts that are unverified or already suspended.

Instructions

Suspend a customer: blocks sign-in and ends every live session. Orders and carts stay. Refused for an account that has not verified yet or is already suspended.

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": {
      "id": "<id>"
    },
    "name": "suspend_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe customer's id (from list_customers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds genuinely new behavioral detail: sessions are terminated, but orders and carts survive, plus two refusal conditions. That is strong context beyond the structured hints, though it doesn't say whether the suspension is reversible or how the agent recovers from a refusal.

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, zero filler, with the primary effects front-loaded before the exception conditions. Every clause carries operational 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 mutation with no output schema, the definition covers the action, the side effects, the state that survives, and the failure preconditions. Nothing an agent needs in order to decide and invoke correctly is missing.

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% and the single 'id' parameter is already documented with its provenance ('from list_customers') in the schema itself. The description adds no further meaning about the identifier, so the baseline of 3 applies for a one-parameter tool whose schema does the work.

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?

Names a specific verb and resource ('Suspend a customer') and immediately enumerates the concrete effects: sign-in blocked, live sessions ended, orders and carts preserved. That distinguishes it from unsuspend_customer and from destructive delete-style siblings without ambiguity.

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?

Gives explicit preconditions for refusal — unverified account or already-suspended account — which tells the agent when the call will fail and implies when not to attempt it. It stops short of naming unsuspend_customer as the inverse operation, so routing for the reverse case is left to inference.

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