Skip to main content
Glama
Sign In
Mainframe MCP Server

Mainframe MCP Server

by rohittrimale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

search_seq_datasets

Read-only

Search sequential datasets by filter and optionally by content, with support for regex and case sensitivity.

Instructions

Search sequential datasets matching filter for optional content.

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": {
      "filter": "<filter>"
    },
    "name": "search_seq_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterYes
contentNo
max_resultsNo
regex_contentNo
case_sensitiveNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations indicate readOnly, openWorld, non-destructive, but the description does not elaborate on behavioral traits such as pagination, result ordering, or the effect of the 'content' parameter. It adds minimal value beyond annotations.

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 sentence, which is concise, but the phrasing 'matching filter for optional content' is grammatically awkward and could be clearer. It achieves brevity at the expense of clarity.

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?

With 5 parameters, 0% schema coverage, and no output description (despite having an output schema), the description fails to provide sufficient context for correct invocation. It lacks details on parameter roles, result format, and edge cases.

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 explanation of any parameter (filter, content, max_results, regex_content, case_sensitive). The meaning and usage of each parameter are entirely absent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Search sequential datasets matching filter for optional content.' It identifies the resource (sequential datasets) and action (search), but the phrasing is awkward and the role of 'filter for optional content' is unclear. It distinguishes from siblings only by name; no further differentiation.

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 scan_source. No when-not or context provided.

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