Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Unsuspend customer

unsuspend_customer
Destructive

Restore sign-in access for a suspended customer and clear any lockout; rejects requests when the customer is not suspended.

Instructions

Let a suspended customer sign in again and clear any lockout. Refused for a customer who is not 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": "unsuspend_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe customer's id (from list_customers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation profile is known. The description adds the refusal-on-non-suspended-customer behavior, which goes beyond the annotations, but it says nothing about side effects — whether the customer is notified, whether prior suspension history is retained, or what makes this operation 'destructive'.

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

Conciseness4/5

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

Two short sentences with no filler; the action comes first and the precondition second in a logical order. Nothing is wasted, though the second sentence could have been folded into the first without loss.

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

Completeness3/5

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

For a one-parameter mutation with no output schema and annotations covering the safety profile, the description covers purpose and one precondition. It is still missing the boundary against unlock_customer and any statement about observable results, which matter for a state-changing call.

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?

There is a single parameter at 100% schema description coverage, and the schema already explains it is the customer id sourced from list_customers. The description adds no format, sourcing, or validation detail beyond that, so the baseline of 3 applies.

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+resource: re-enabling sign-in for a suspended customer and clearing lockouts. It is clear on its own, but it does not distinguish itself from the sibling tool unlock_customer, which on its face also concerns clearing a lockout — an agent could plausibly confuse the two.

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 gives one useful exclusion: the call is "Refused for a customer who is not suspended," which tells the agent a precondition to check. However, it names no alternative for that case (get_customer, unlock_customer, suspend_customer), so the agent is left to infer the recovery path when the precondition fails.

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