Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Resend customer verification

resend_customer_verification
Destructive

Issue a fresh 24-hour verification token to a pending customer and notify them by webhook or Cmssy email. The previous token is invalidated; verified or suspended customers are refused.

Instructions

Issue a fresh verification token for a customer whose status is pending and send it as the webhook event account.verification_requested to the workspace's webhooks; when the customer's model has account emails on (get_model auth.email.enabled), cmssy also emails the customer itself. The previous token stops working and the new one lasts 24 hours. Refused for a customer who is already verified or is suspended, and after five account requests for the same customer in an hour. emailDelivery.status is cmssy's own email: SENT (handed to the email provider), FAILED (not sent - error says why, the email log lists it) or OFF (the model leaves emailing to the app). endpointSubscribed: false means no enabled webhook endpoint receives the event; with emailDelivery OFF nothing then reaches the customer.

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": "resend_customer_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe customer's id (from list_customers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the side effects that matter: the previous token stops working, the new token lasts 24 hours, a webhook event is emitted, and there is a five-per-hour rate limit with refusal conditions. It also explains the meaning of emailDelivery.status values and endpointSubscribed, which the agent cannot learn elsewhere since there is no output schema.

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?

The description is dense but front-loaded: the core action and delivery mechanism come first, then refusal conditions, then return-field semantics. Some sentences pack multiple clauses (the emailDelivery.status sentence especially), but each carries distinct information rather than restating the name or annotations.

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?

With one simple parameter, no output schema, and only coarse annotations, the description carries the full burden and does: it covers preconditions, side effects, rate limits, delivery channels, and how to interpret the resulting delivery fields. Nothing an agent needs in order to call it correctly or interpret the outcome 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 coverage is 100% and the single `id` parameter is already documented with its source (list_customers). The description adds only the implicit precondition that the id must refer to a pending customer, not new syntax or format detail, so the baseline of 3 applies.

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 opens with a specific verb+resource: 'Issue a fresh verification token for a customer whose status is pending'. It scopes the resource narrowly (pending customers, verification tokens) and enumerates the delivery path (webhook event account.verification_requested, plus optional email), so an agent can distinguish it from related customer tools like send_customer_password_reset without opening the schema.

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?

Clear preconditions and exclusions are stated: the customer must be pending, and the call is refused if the customer is already verified or suspended, or after five requests in an hour. What's missing is explicit routing to an alternative (e.g., a password-reset tool for a different intent), so it stops short of a 5.

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