Skip to main content
Glama
ebcdicjp-mcp

ebcdicjp-mcp

by yukijames25

describe_layout

Parse a COBOL copybook and list every field's byte position, length, and type, including PIC X, PIC N, zoned, packed, and binary fields.

Instructions

Parse a COBOL copybook and list every field with its byte position, length and type (text = PIC X with SO/SI kanji, dbcs = PIC N, zoned, packed = COMP-3, binary = COMP).

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": {
      "copybook": "<copybook>"
    },
    "name": "describe_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordNo
copybookYesAbsolute path to the COBOL copybook
copybook_encodingNoauto = UTF-8, else Shift_JIS (cp932)auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole behavioral burden. It implies a read-only parse and usefully defines the type taxonomy (PIC X/SO-SI kanji, PIC N, zoned, COMP-3, COMP), but says nothing about side effects, encoding fallback behavior, failure modes for malformed copybooks, or output ordering.

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?

A single front-loaded sentence with no filler, and the parenthetical type legend genuinely earns its space by defining domain terms. The mapping list is dense but readable; nothing is redundant.

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?

With no output schema and no annotations, the description must do more, and it does cover the return shape well ('every field with its byte position, length and type'). It leaves out what 'record' selects and what happens on unparseable input, which are material gaps for a 3-parameter parsing tool.

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

Parameters3/5

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

Schema coverage is 67% and the description adds no parameter-level meaning at all — notably the undocumented 'record' parameter and when to supply it are never addressed. With most parameters already described in the schema, the baseline of 3 applies, but the description does not compensate for the gap.

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?

States a concrete verb+resource ('Parse a COBOL copybook') and the exact result shape ('list every field with its byte position, length and type'), which lets an agent picture the output. It does not reference any sibling or state how it differs from read_records/decode_bytes, so it falls short of full differentiation.

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?

Usage is only implied: an agent can infer this is for inspecting a copybook's field layout, but there is no explicit when-to-use, no prerequisites (e.g. file must exist/is readable), and no pointer to the sibling that handles actual record reading.

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