Skip to main content
Glama
Sign In
Mainframe MCP Server

Mainframe MCP Server

by rohittrimale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_gdg_versions

Read-only

Retrieve a list of all versions for a specified GDG base dataset, showing each generation.

Instructions

List generations of a GDG base (via LISTCAT).

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": {
      "gdg_base": "<gdg_base>"
    },
    "name": "get_gdg_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
gdg_baseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description's mention of 'via LISTCAT' adds technical context but does not elaborate on behavioral aspects like output format or error handling. Value added is moderate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the core purpose. However, it could be slightly more structured with separate usage and parameter notes.

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?

For a tool with a specialized concept (GDG) and an output schema that may explain return values, the description provides the essential action but leaves out context about what generations are and when to use this over similar tools. Adequate but not complete.

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 must explain the parameter. It mentions 'gdg_base' but does not define what a GDG base is or specify naming conventions, leaving the agent with insufficient semantic detail.

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?

The description clearly states the tool lists generations of a GDG base via LISTCAT, with a specific verb and resource. While it distinguishes from siblings like get_dataset_list, it could be more explicit about what 'generations' means in the context of GDGs.

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 versus alternatives like get_dataset_list or search_seq_datasets. There are no prerequisites or context for when this tool is appropriate.

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