Skip to main content
Glama
Sign In

Hovercode

by com.hovercode
OverviewDiscussionsAdmin

delete_folder

DestructiveIdempotent

Delete a folder. The codes in it (and in its subfolders) are NOT deleted — they become unfiled — and its subfolders move up to its parent.

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": {
      "id": "<id>"
    },
    "name": "delete_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFolder id (from list_folders).

Output Schema

NameRequiredDescriptionDefault
idNo
errorNoPresent only when the tool failed (isError): cause, retryable, message.
deletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / error / additionalProperties
      Removed value: -true
    • changedOutput schema / properties / error / description
      Previous value: -"Present only when the tool failed (the result is also flagged isError)."New value: +"Present only when the tool failed (isError): cause, retryable, message."
    • removedOutput schema / properties / error / properties
      Removed value: -{
-  "cause": {
-    "description": "Machine-readable failure category: invalid_argument, not_found, forbidden, plan_limit, rate_limited, or server_error.",
-    "type": "string"
-  },
-  "message": {
-    "type": "string"
-  },
-  "retryable": {
-    "description": "Whether repeating the same call could succeed.",
-    "type": "boolean"
-  }
-}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "deleted": {
+      "type": "boolean"
+    },
+    "error": {
+      "additionalProperties": true,
+      "description": "Present only when the tool failed (the result is also flagged isError).",
+      "properties": {
+        "cause": {
+          "description": "Machine-readable failure category: invalid_argument, not_found, forbidden, plan_limit, rate_limited, or server_error.",
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retryable": {
+          "description": "Whether repeating the same call could succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "id": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare destructiveHint and idempotentHint, but the description adds critical non-obvious cascade semantics: codes become unfiled, subfolders reparent to the parent. This is exactly the kind of side-effect disclosure that supersedes a bare destructive flag.

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 tight sentence pair: the action, then the non-obvious cascade behavior. Every clause earns its place.

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?

Output schema exists so return values need not be explained. With a fully documented single param, annotations covering safety, and explicit cascade semantics, nothing an agent needs is missing.

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 coverage is 100% and the single 'id' parameter already documents its origin ('from list_folders'), so the baseline of 3 applies. The description adds no parameter details beyond the schema.

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?

Specific verb 'Delete' applied to the resource 'folder' with a precise statement of what happens to contained codes and subfolders. Clearly distinguishable from delete_page, delete_qr_code, and delete_short_link siblings.

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 implied by the destructive verb and no alternatives are needed for deletion, but the description doesn't state prerequisites (e.g., does the folder need to be empty, are there permission requirements). Adequate but with a gap.

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

All Hovercode toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources