MCP Server By TestMu AI

Delete User File

deleteUserFile

Destructive

Delete an uploaded user file by stored TestMu AI file path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deleteUserFile"
  }
}

Input Schema

Name	Required	Description	Default
`filePath`	No	Key of the stored user file, as uploadUserFile returns it (usually the file name)
`file_path`	No	Key of the stored user file, as uploadUserFile returns it (usually the file name)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026

changedInput schema / properties / filePath / description

Previous value: -"Stored LambdaTest file path to delete"New value: +"Key of the stored user file, as uploadUserFile returns it (usually the file name)"

changedInput schema / properties / file_path / description

Previous value: -"Stored LambdaTest file path to delete"New value: +"Key of the stored user file, as uploadUserFile returns it (usually the file name)"

First observedOct 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful tie-in to uploadUserFile ('as uploadUserFile returns it'), but says nothing about permanence, behavior when the file is missing, or who may delete a file.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is efficient, though it is short enough that the missing usage and safety context has nowhere to live.

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 destructive delete with no output schema, the description should mention irreversibility and what the response reports. It instead covers only the identifier, leaving the agent to infer the rest from annotations.

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%, so both parameters are documented and the baseline of 3 applies. The description adds only that the key comes from uploadUserFile; it does not resolve the notable ambiguity of two parallel keys (filePath vs file_path), neither of which is required.

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?

States a specific verb and resource ('Delete an uploaded user file') plus the identifier used ('stored TestMu AI file path'). It implicitly separates itself from deleteUploadedApps and deletePrerunFile by saying 'user file', but never names those siblings or draws the line 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?

No when-to-use or when-not guidance. With near-identical siblings (deletePrerunFile, deleteUploadedApps) an agent has no stated rule for choosing this tool over them.

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

All MCP Server By TestMu AI tools Inspect

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

Need Help?