Skip to main content
Glama
Sign In
Mainframe MCP Server

Mainframe MCP Server

by rohittrimale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_dataset

Destructive

Permanently delete a mainframe dataset. The operation is irreversible and requires the confirm flag set to true.

Instructions

Delete a mainframe dataset. IRREVERSIBLE. Requires confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
dataset_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark destructiveHint=true, and the description adds 'IRREVERSIBLE' and the confirm requirement, reinforcing that this is a destructive, non-recoverable action.

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 sentences, no wasted words, front-loaded with the key action and constraints.

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?

The description is brief but covers core intent, irreversibility, and prerequisite. An output schema exists, so return details are not needed here. Still, it could mention consequences or error conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains that confirm must be true, which adds meaning beyond the schema (where confirm defaults to false). Schema coverage is 0%, so the description compensates well.

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?

The description clearly states 'Delete a mainframe dataset,' which is a specific verb and resource. It distinguishes itself from sibling tools like create_dataset, rename_dataset, etc.

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 description mentions 'Requires confirm=true,' which gives a specific condition for use, but does not provide when-not-to-use or compare with alternatives.

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

Deploy Server

Other Tools