Skip to main content
Glama
Sign In
Mainframe MCP Server

Mainframe MCP Server

by rohittrimale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

submit_jcl_string

Submit raw JCL text directly to JES for job execution on z/OS mainframes.

Instructions

Submit raw JCL text directly to JES.

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": {
      "jcl_text": "<jcl_text>"
    },
    "name": "submit_jcl_string"
  }
}

Input Schema

NameRequiredDescriptionDefault
jcl_textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations (readOnlyHint=false, openWorldHint=true) indicate write operations with potential side effects, but the description does not elaborate on what happens upon submission (e.g., job queued, job ID returned). No additional behavioral context beyond stating the action.

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

Conciseness3/5

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

The description is a single concise sentence, but it is too brief given the tool's purpose. It could include essential details without losing conciseness.

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 only one parameter and an output schema, the description fails to explain the return value or workflow context (e.g., job tracking). It is incomplete for effective use.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no additional meaning for the required 'jcl_text' parameter beyond the name. No format, constraints, or examples are given, leaving the agent without guidance.

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 the verb 'submit' and resource 'raw JCL text' with target 'JES'. It effectively distinguishes from sibling tool 'submit_job' which submits a JCL member from a dataset, making the unique purpose evident.

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 submit_job. No mention of prerequisites, when not to use, or context for selection. The description offers no usage guidance.

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