Skip to main content
Glama
Sign In
saas-alerts-mcp

saas-alerts-mcp

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

saas_alerts_customers_delete

Destructive

Permanently delete a SaaS Alerts customer and all associated data. Irreversible action—confirm with user before deletion.

Instructions

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a SaaS Alerts customer and all associated data. This action cannot be undone. Confirm with the user before invoking.

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": {
      "customer_id": "<customer_id>"
    },
    "name": "saas_alerts_customers_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idYesCustomer ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true), the description discloses that all associated data is permanently deleted and the action cannot be undone. This adds meaningful context about cascading effects and the need for confirmation.

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?

The description is a single concise sentence with a leading warning icon, front-loading the critical destructive nature. Every word contributes to the safety-critical message with no redundancy.

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?

Given the tool's simplicity (one parameter, no output schema) and strong annotations, the description fully covers the essential safety aspects: irreversibility, data scope, and user confirmation. No further return-value or error documentation is necessary for this delete operation.

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?

The input schema already documents customer_id with 'Customer ID to delete' (100% coverage). The description adds no additional format, source, or prerequisite details for the parameter, so it remains at baseline.

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 the specific verb 'deletes' and names the resource 'SaaS Alerts customer' with scope 'all associated data'. It clearly distinguishes from sibling create/update/list/get tools by describing the destructive action.

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?

The description provides clear context for use by warning that the action is destructive, irreversible, and requires user confirmation. It does not explicitly name non-destructive alternatives, but the strong warning makes the appropriate usage unambiguous.

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