Skip to main content
Glama
Sign In
Mainframe MCP Server

Mainframe MCP Server

by rohittrimale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

recall_dataset

Recall a migrated dataset from tape or HSM back to disk for immediate access.

Instructions

Recall a migrated dataset from tape/HSM back to disk.

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": "recall_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataset_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already provide readOnlyHint: false, destructiveHint: false. The description adds no behavioral details (e.g., whether data on tape is preserved, duration, or error conditions).

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?

Single sentence with 8 words, front-loading the core action and resource. No extraneous information.

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?

Despite having an output schema, the description lacks crucial context like prerequisites, state requirements, and post-conditions. Tool is simple but minimal guidance hurts usability.

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?

With 0% schema description coverage, the description should clarify parameter meaning. It only says 'dataset_name' but provides no detail on format, naming conventions, or examples.

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 uses a specific verb 'recall' and resource 'migrated dataset from tape/HSM back to disk', clearly distinguishing it from sibling tools like create/delete/rename, which operate differently.

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?

No guidance on when to use this tool vs alternatives. It does not specify prerequisites (e.g., dataset must be migrated) or warn against using on online datasets.

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