Skip to main content
Glama

Delete storage object

storage_delete_object
DestructiveIdempotent

Delete an object from app storage

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": {
      "key": "<key>"
    },
    "name": "storage_delete_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds no behavior beyond the annotations – nothing about whether deletion is permanent, what happens if the key is absent, or what error conditions arise.

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 short sentence with no filler, front-loaded with the verb. It is efficient, though its brevity is achieved by omitting useful detail rather than by disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, irreversible-looking deletion tool with no output schema and an undocumented required parameter, the description leaves too much unstated. An agent cannot tell whether the key must exist, whether its container is implied, or what a successful delete returns.

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 description coverage is only 50%: the required 'key' parameter has no description in the schema, and the description does not explain its format or namespace. With a low coverage ratio, the description was expected to compensate and does not.

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 verb and resource ('Delete an object from app storage'), which is clear enough for an agent to know the operation. It does not, however, distinguish this from sibling deletion tools like delete_file or delete_share_link, so the agent must infer that 'app storage' means the key-value/object store rather than a file tree.

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 guidance on when to use this versus delete_file or delete_share_link, nor any stated prerequisite such as needing a project context. The only hint about project scoping lives in the schema's project_id description, not in the tool description itself.

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.

Resources