Skip to main content
Glama
Sign In
forge

forge

by SoulNassim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

workspace_delete

Moves a file or folder to the workspace's .trash/ for recoverable deletion, helping prevent accidental loss of project assets.

Instructions

Move a file or folder to the workspace's .trash/ (recoverable).

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": {
      "path": "<path>"
    },
    "name": "workspace_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath relative to the workspace root.
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the single most important trait — deletion is a soft move into .trash/ and is recoverable — but says nothing about overwrite behavior for an existing trash entry, whether folders are moved recursively, permission requirements, or what happens when the path does not exist.

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?

A single tight sentence that front-loads the verb and resource and puts the recoverability caveat immediately after. Nothing is wasted and nothing is buried.

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 two-parameter tool with no annotations and no output schema, the description covers the core semantics adequately but leaves the 'project' parameter and failure/edge-case behavior unexplained. It is serviceable but not complete.

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 50%: 'path' is documented in the schema but 'project' is completely undocumented in both schema and description. The description adds no meaning about how path is resolved relative to the workspace root or how project scopes the operation, so it does not compensate for the coverage gap.

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?

The description names a specific operation (move to the workspace's .trash/) applied to a specific resource (file or folder), and the parenthetical clarifies this is the delete-equivalent. It implicitly distinguishes itself from the sibling workspace_move by naming a fixed destination rather than a caller-specified one, though it never says so explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the sibling workspace_move, which an agent could easily confuse with this tool. The '(recoverable)' note hints that no destructive-confirmation ritual is needed, but that is inference rather than stated guidance.

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