Skip to main content
Glama
ebcdicjp-mcp

ebcdicjp-mcp

by yukijames25

encode_text

Encodes text to Japanese EBCDIC hex for IBM930/IBM939, adding SO/SI around kanji and listing unencodable or one-way characters.

Instructions

Encode text to Japanese EBCDIC hex (SO/SI added around kanji). Lists unencodable and one-way characters.

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": {
      "text": "<text>"
    },
    "name": "encode_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
codepageNoibm930 = katakana in single-byte (no lowercase); ibm939 = Latin with lowercase. auto detects it and says what it assumed in notes.auto
dbcs_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the core transformation behavior: SO/SI bytes are inserted around kanji and problematic characters are reported. It does not state whether the operation can fail, what the notes/assumptions output looks like in detail, or how 'one-way' characters affect round-tripping.

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?

Two tight sentences, front-loaded with what the tool produces and followed by a related-behavior note. No filler or restatement of the tool name.

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?

There is no output schema, and the description partially covers return values by saying unencodable and one-way characters are listed, but it does not describe the hex string's shape. The undocumented dbcs_only parameter is a real gap for a three-parameter tool with no annotations.

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?

Schema coverage is only 33%: codepage is documented in the schema, but dbcs_only has no description in either place, and the description never mentions either parameter. The description therefore adds no meaning beyond the one parameter the schema already explains, leaving a control flag completely opaque.

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 names a specific verb (encode) and a precise target format (Japanese EBCDIC hex), and adds a concrete detail (SO/SI around kanji) that distinguishes it from the inverse decode_bytes sibling. It stops short of explicitly naming the counterpart tool, but the purpose is unambiguous.

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?

There is no when-to-use guidance, no mention of when to prefer decode_bytes or describe_layout, and no note about which path to take with write_records. Usage is only implied by the name and first sentence, and the codepage-selection guidance lives entirely in the schema rather than the description.

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