Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete form

delete_form
Destructive

Permanently deletes a form and all its submissions by id or slug, removing the form and associated data from the workspace.

Instructions

Permanently delete a form and all its submissions.

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_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
idOrSlugYesThe form'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.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description still adds real value by disclosing that the deletion is permanent and cascades to all submissions, which the annotations alone do not convey. It does not mention whether authentication or elevated permissions are required, or whether the delete can be undone.

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?

One short sentence with no wasted words, and the critical word "Permanently" is front-loaded so the destructive nature registers immediately.

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 safety and a fully documented schema, this is nearly complete. The only missing element is the authentication or confirmation requirement for an irreversible action.

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 schema has 100% description coverage and documents the single idOrSlug parameter, so the baseline is 3. The description gives no additional detail such as the expected format of a slug, whether an id is preferred, or what error occurs on a miss.

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?

Uses a specific verb ("Permanently delete") and resource ("a form and all its submissions"), and the scope clause implicitly distinguishes it from delete_form_submission, which handles a single submission. It never names that sibling, so the differentiation must be inferred rather than being spelled out.

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: a reader derives that this is the tool for removing a whole form rather than one submission. There is no explicit statement of when to prefer an alternative (e.g., deleting submissions individually) and no stated prerequisites or confirmation requirements.

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