Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Delete Remote Tool

amount.delete_remote

Permanently deletes one offloaded remote file from the storage mount without touching the local copy; requires confirm=true only after the user approves that exact file.

Instructions

DESTRUCTIVE and irreversible: delete one offloaded object from the storage mount and forget it (the local file is not touched). Refused unless confirm=true, so first tell the person exactly which file (amount.files) will be deleted and call with confirm=true only after they agreed. If the file exists only remotely, it is gone for good.

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": "<file>",
      "confirm": "<confirm>"
    },
    "name": "amount.delete_remote"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesFile id from amount.files
confirmYesMust be true, set only after the person confirmed this exact file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, so the description carries the behavioral burden and does so well: it discloses irreversibility, the confirm gate and its refusal behavior, that the local file is untouched, and that a remote-only file is gone permanently. This is exactly the context an agent needs before a destructive call.

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 sentences, front-loaded with the DESTRUCTIVE warning, then the confirm protocol, then the permanence caveat. No filler; every sentence adds a distinct constraint.

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 two-parameter destructive tool with no output schema, the description covers safety profile, preconditions, scope, and consequences. Nothing an agent needs in order to call it correctly 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 schema already documents both parameters, including that confirm must be true only after the person confirmed the exact file. The description largely restates that, adding only the amount.files provenance hint, so 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 and resource ('delete one offloaded object from the storage mount') and immediately bounds the scope: the local file is not touched. An agent can distinguish this from sibling listing tools like amount.files without opening the 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?

Gives a clear precondition and workflow: refused unless confirm=true, tell the person which file first, then call with confirm=true only after agreement. It points to amount.files for identifying the file. It does not name an explicit alternative tool for non-destructive cases, so it falls just short of a 5.

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