Skip to main content
Glama
ebcdicjp-mcp

ebcdicjp-mcp

by yukijames25

decode_bytes

Decodes hex bytes as Japanese EBCDIC text and lists decoding problems, helping diagnose hex dumps or error messages.

Instructions

Decode hex bytes (e.g. from a hex dump or an error message) as Japanese EBCDIC, with problems listed.

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": {
      "hex": "<hex>"
    },
    "name": "decode_bytes"
  }
}

Input Schema

NameRequiredDescriptionDefault
hexYes
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.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden; it discloses that decoding may produce a list of problems and that the target is Japanese EBCDIC. It does not state side effects, error behavior for invalid hex, or the shape of the result, but the operation is inherently a read/decode utility.

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?

The single sentence is front-loaded with the action and resource, and includes only useful context. There is no filler or repetition.

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?

For a tool with three parameters, low schema coverage, no annotations, and no output schema, the description is too thin. It leaves dbcs_only, hex formatting, and the returned problem list unexplained.

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 description coverage is only 33%: hex has no format guidance and dbcs_only is not explained at all in the schema or description. The description adds the Japanese EBCDIC context but does not compensate for the undocumented parameters.

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 gives a specific verb and resource ('Decode hex bytes') and narrows the encoding to Japanese EBCDIC. It is clear what the tool does, though it does not explicitly distinguish itself from the detect_codepage or encode_text siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The examples 'from a hex dump or an error message' provide clear usage context for when this decoder is relevant. It does not state exclusions or when to prefer a sibling such as detect_codepage, so it falls short of full routing guidance.

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