Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete model

delete_model
Destructive

Permanently removes a data model by its ID or slug, cascading deletion to all records of that model. Use when you need to eliminate a model and its associated data.

Instructions

Delete a data model. WARNING: this cascades - ALL records of the model are permanently deleted.

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": {
      "idOrSlug": "<idOrSlug>"
    },
    "name": "delete_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
idOrSlugYesThe model's id or slug to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "idOrSlug"
      +]
  2. First observedv0.73.1

TDQS

A3.8/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, so the safety profile is covered structurally. The description adds the key fact annotations cannot express: the deletion cascades and ALL records of the model are permanently removed, which is exactly the kind of consequence an agent needs before invoking it. It could go further by noting related entities or permission requirements.

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?

Two sentences, zero padding, and the destructive scope is front-loaded in capital letters immediately after the purpose statement. Every sentence earns its place.

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

Completeness4/5

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

For a one-parameter destructive tool with annotations covering the safety signals and no output schema to explain, this is nearly complete. The only gap is what else may be affected by the cascade (e.g., dependent records or references) and whether the action is recoverable.

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?

With 100% schema description coverage on the single idOrSlug parameter, the schema already explains that an id or slug is accepted. The description adds no format, lookup, 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?

"Delete a data model" states a specific verb and a specific resource, and the resource (model) is distinguishable from sibling delete tools that target records, carts, forms, or media. It stops short of contrasting itself against a sibling like delete_record, but the object is unambiguous.

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?

Usage is only implied: an agent understands this is the way to remove a model, but the description gives no explicit when-to-use/when-not guidance and no pointer to alternatives for deleting only records versus the whole model. The cascade warning at least gives context for the decision.

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