Skip to main content
Glama

delete_dataset

Deletes a dataset created by upload_dataset and refuses removal while an unfinished job is using it, so you can clean up Kaggle datasets safely.

Instructions

Delete a dataset created by upload_dataset. Refuses if an unfinished job uses it.

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": {
      "ref": "<ref>"
    },
    "name": "delete_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one important failure mode — the call is refused when an unfinished job references the dataset — but omits irreversibility, required permissions, and what happens to datasets still referenced by finished jobs.

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?

Two short sentences, front-loaded with the action and provenance, followed by the one guardrail an agent most needs. No filler.

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?

The output schema covers return values, keeping the burden low, but for a destructive single-parameter tool the description should at least identify what 'ref' expects and whether deletion is permanent. The safety/precondition side is partially covered; the input contract is not.

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 0% for the single required parameter 'ref', and the description never explains what a ref is — an ID, a name, or a path — nor the format expected. The only hint is indirect, via the reference to datasets created by upload_dataset.

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 ('Delete') and resource ('dataset') and narrows the scope to datasets produced by upload_dataset, which ties it to a known sibling without ambiguity. An agent can tell immediately what object class this operates on and where those objects come from.

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?

Usage is implied rather than stated: you delete a dataset you previously uploaded. The refusal condition ('unfinished job') hints at when the call will fail, but there is no explicit when-to-use versus when-to-use-something-else guidance, such as cleanup_job for job artifacts or list_datasets for inspection.

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