Skip to main content
Glama

Sevana Voice Quality

Delete an upload

delete_upload
Idempotent

Delete an uploaded file now instead of waiting for it to expire.

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": {
      "upload_id": "<upload_id>"
    },
    "name": "delete_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_idYes

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, so the mutation and repeat-safety profile is covered structurally. The description adds the useful timing rationale (skipping expiry), but does not say whether deletion is irreversible, whether downstream jobs referencing the upload are affected, or what happens if the upload already expired.

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?

A single front-loaded sentence with no filler; the differentiator against passive expiry is placed immediately after the action.

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?

An output schema exists, so return values need no explanation, and a one-parameter delete is inherently simple. Still, for a destructive operation with no annotation on reversibility, the description should clarify irreversibility and edge cases like already-expired uploads.

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?

One parameter with 0% schema description coverage, so the description carries the full burden — yet it says nothing about upload_id (format, source, or how to obtain it). The name is mostly self-explanatory, but no meaning is added beyond the schema.

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?

Specific verb+resource ("Delete an uploaded file") with a distinguishing scope note: immediate deletion versus waiting for expiry. It is clearly not create_upload or upload_inline, though it does not explicitly name an alternative deletion path.

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

Usage Guidelines3/5

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

The phrase "now instead of waiting for it to expire" implies when to use it — when prompt cleanup matters. There are no explicit when-not conditions, prerequisites, or named alternatives.

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