Skip to main content
Glama

Modellix Media Generation

modellix_delete_file

DestructiveIdempotent

Permanently delete exactly the explicitly selected file_id after user approval. Never delete other files to free quota automatically. An absent file is a successful already_absent result.

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": {
      "file_id": "<file_id>"
    },
    "name": "modellix_delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYesOne explicitly selected file ID.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructive/not-readOnly/idempotent, and the description adds value on top: permanence of deletion, the human-approval gate, the prohibition on speculative quota cleanup, and the idempotency semantics ('an absent file is a successful already_absent result'). That last clause is exactly the kind of retry-safety context annotations alone cannot convey.

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?

Three short sentences, each carrying a distinct constraint: action and scope, prohibition, and edge-case result. The approval condition is front-loaded and nothing is repeated from the schema.

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?

An output schema exists, so return values need no explanation, and the description still covers the one non-obvious outcome (already_absent). For a single-parameter destructive tool with rich annotations, nothing an agent needs in order to call it safely is missing.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is already documented, so the baseline is 3. The description still adds meaning by constraining the value to one file, explicitly selected by the user, rather than any file the agent infers.

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 and resource ('Permanently delete ... file_id') with scope precision ('exactly the explicitly selected file_id'), leaving no ambiguity about what is removed. It is trivially distinguishable from the sibling upload/list/get operations.

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?

Gives a clear precondition ('after user approval') and an explicit when-not ('Never delete other files to free quota automatically'), which rules out the most likely misuse. It does not name an alternative cleanup path, so it stops short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.