Skip to main content
Glama
Sign In
Backforms MCP

Backforms MCP

by Arneld18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_form

Permanently deletes a form endpoint from your Backforms workspace using its UUID. Use it to remove forms that are no longer needed.

Instructions

Permanently deletes a form endpoint from the Backforms workspace.

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

NameRequiredDescriptionDefault
form_idYesUUID of the form endpoint to permanently delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It importantly discloses that deletion is permanent and scoped to the Backforms workspace, but it omits permissions required, whether associated submissions or webhooks are also removed, and whether any confirmation is needed.

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 definition is a single, front-loaded sentence with no filler. Every word contributes to stating the action, target, and permanence.

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

Completeness3/5

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

For a simple one-parameter destructive tool, the description covers the core action and irreversibility. However, with no annotations or output schema, it should say more about blast radius and permissions to be fully complete.

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 description coverage is 100%: form_id is already documented as the UUID of the form endpoint to permanently delete. The description adds no further parameter meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 gives a specific verb ("permanently deletes") and resource ("form endpoint") with workspace scope. It distinguishes itself from siblings like create_form, list_forms, update_form_settings, and get_form_details by clearly being the destructive removal operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states what the tool does but offers no guidance on when to use it versus alternatives, no prerequisites, and no when-not-to-use conditions. An agent must infer that this is for removing a form endpoint rather than updating or inspecting it.

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