Skip to main content
Glama

Delete a recording

delete_cpet
DestructiveIdempotent

Delete an uploaded recording immediately, instead of at its 24 h expiry.

For when the user has finished with a recording, particularly clinical data. It cannot be undone: the uploaded file was discarded at parsing, so analysing the recording again takes a new upload.

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": {
      "cpet_id": "<cpet_id>"
    },
    "name": "delete_cpet"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpet_idYesHandle from upload_cpet, create_upload or get_sample_cpet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cpet_id / description
      Added value: +"Handle from upload_cpet, create_upload or get_sample_cpet."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, yet the description still earns credit by disclosing the concrete data consequence: the uploaded file was discarded at parsing, so the recording cannot be re-analysed without a fresh upload. That tells the agent exactly what is lost, which the boolean flags do not.

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, front-loaded with the action and its timing distinction, then the use case, then the irreversible consequence. Nothing is repeated and nothing is padding.

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

Completeness4/5

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

For a one-parameter irreversible delete with full annotation coverage and no output schema, the description covers purpose, timing, and consequences adequately. The only thing an agent might still want is the response shape on success or on an invalid handle, though that is a minor omission at this complexity.

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?

Only cpet_id is accepted and the schema already describes it at 100% coverage, naming its provenance (upload_cpet, create_upload, get_sample_cpet). The description adds no format, constraint, or validation guidance beyond that, so this sits at the schema-backed baseline.

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?

"Delete an uploaded recording immediately, instead of at its 24 h expiry" gives a specific verb, a specific resource, and a scope qualifier (immediate vs automatic expiry) that separates it from the sibling get_/upload_/analyze_ tools without naming them.

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?

It states the triggering condition plainly: "For when the user has finished with a recording, particularly clinical data." The note that re-analysis requires a new upload implicitly tells the agent when not to call it, but no explicit alternative or exclusion is spelled out.

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