nc-mcp-server

delete_form

DestructiveIdempotent

Remove a form and all its associated questions, options, shares, and submissions by providing its numeric form ID.

Instructions

Delete a form, including all questions, options, shares, and submissions.

Args: form_id: Numeric form id.

Returns: Confirmation with the deleted id.

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": {
      "form_id": "<form_id>"
    },
    "name": "delete_form"
  }
}

Input Schema

Name	Required	Description	Default
`form_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds critical context by specifying the full scope of destruction (all questions, options, shares, submissions), which is not in the annotations. This warns the agent of the broad impact beyond just deleting a single entity. It doesn't mention irreversibility, but that is implied by destructiveHint.

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 extremely concise: one sentence for the main action, followed by a simple Args/Returns format. All information is front-loaded, with no filler or redundancy. 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 single-parameter delete tool, the description covers the destructive scope, the parameter, and the return value. The annotations provide the safety profile. The only missing context is a note on irreversibility or permission requirements, but those are likely implied by the destructive annotation. Overall, it is complete enough for an agent to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate for the parameter. However, it merely restates the schema type ('Numeric form id') without adding semantics like what the ID refers to or any validation. The description adds no meaningful guidance beyond what the integer type already conveys. It could clarify that form_id is the unique identifier of the form to delete, but it does not.

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 a clear verb ('Delete') and resource ('form'), and explicitly lists the cascading scope (questions, options, shares, submissions). This distinguishes it from sibling tools like delete_question or delete_option, leaving no ambiguity about what is removed.

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?

The purpose is self-evident, but the description does not mention when to prefer this over alternatives or when not to use it. It implicitly assumes the agent knows to use it for deleting a form, but lacks explicit exclusion or alternative guidance. The cascade warning partially serves as a caution, but not as usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server