Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

files_delete

DestructiveIdempotent

Permanently delete files from this workspace by their IDs (generated documents, uploads, screenshots, etc.).

IRREVERSIBLE: removes the DB record, detaches every reference (knowledge collections, thread pins, message attachments), and deletes the stored blob. There is no undo.

Use to clean up leftover / superseded generated files. Only files that belong to this workspace are touched; unknown or other-workspace ids are returned under not_found. Max 20 per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idsYesList of file IDs to permanently delete (max 20).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/idempotentHint annotations by spelling out exactly what is destroyed (DB record, knowledge-collection references, thread pins, message attachments, stored blob), that there is no undo, that only same-workspace files are touched, and that foreign/unknown IDs surface under `not_found`. That is precisely the extra context annotations cannot carry.

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 irreversible warning is front-loaded and capitalized, followed by the intended use and the edge-case behavior in three tight sentences. No filler, every sentence carries load.

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?

For a destructive 2-param tool with no output schema, the description covers safety, scope, batch limit, and the partial-failure return bucket (`not_found`), which is the one return-value detail an agent actually needs. Nothing material 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 description coverage is 100%, so both parameters (file_ids, in_workspace) are already documented in the schema. The description mainly restates the max-20 limit and the workspace scoping, adding little semantic detail the schema lacks; baseline 3 applies.

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?

States a specific verb (permanently delete), resource (files), scope (this workspace, by IDs) and enumerates what kinds of files it covers. It is trivially distinguishable from siblings like files_upload, files_read, or search_files without opening any schema.

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

Usage Guidelines4/5

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

"Use to clean up leftover / superseded generated files" gives a clear positive trigger and implicitly excludes active/referenced files. It does not name alternatives (e.g., collections_remove_file for detaching rather than deleting), so it stops just short of full when-not guidance.

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

All dialogbrain 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