Skip to main content
Glama
noor202401938-netizen

cyber-chef-mcp

by noor202401938-netizen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cyberchef_from_hex

Decode hexadecimal byte strings into UTF-8 text or raw character data, handling contiguous hex, spaces, 0x prefixes, and comma delimiters.

Instructions

Converts a hexadecimal byte string back into UTF-8 text or raw character data. Supports raw contiguous hex, space-separated bytes, 0x prefixes, and comma delimiters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesHexadecimal string to decode (e.g., '48656c6c6f', '48 65 6c 6c 6f', or '0x480x650x6c0x6c0x6f').
delimiterNoOptional delimiter used between hex bytes. Allowed values: 'None' (default, contiguous hex), 'Space' ('48 65'), '0x' ('0x480x65'), or 'Comma' ('48,65').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.2
    • changedInput schema / properties / delimiter / description
      Previous value: -"Delimiter between hex bytes"New value: +"Optional delimiter used between hex bytes. Allowed values: 'None' (default, contiguous hex), 'Space' ('48 65'), '0x' ('0x480x65'), or 'Comma' ('48,65')."
    • changedInput schema / properties / input / description
      Previous value: -"Hex string (e.g. '48656c6c6f' or '48 65 6c 6c 6f' or '0x480x65')"New value: +"Hexadecimal string to decode (e.g., '48656c6c6f', '48 65 6c 6c 6f', or '0x480x650x6c0x6c0x6f')."
  2. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains the conversion direction and accepted input formats, which is helpful, but it does not disclose behavior for invalid hex input, non-UTF-8 byte sequences, or exactly how 'raw character data' is returned.

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 description is two concise sentences with no filler. The core action is front-loaded, and the supported format details are presented compactly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple conversion tool with a well-documented schema, the description is nearly complete. It states the input, output, and accepted formats. The main gap is the lack of explicit error-handling or edge-case behavior, but this is minor given the tool's low complexity.

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 description coverage is 100%, so the schema already documents both parameters with examples and enum values. The description's mention of supported formats ('raw contiguous hex, space-separated bytes, 0x prefixes, comma delimiters') largely duplicates the schema's delimiter documentation without adding new meaning.

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 states a specific verb ('Converts'), a clear resource ('hexadecimal byte string'), and the output ('UTF-8 text or raw character data'). It clearly distinguishes this from sibling tools like cyberchef_to_hex by indicating the reverse direction.

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?

The description implies when to use the tool: whenever hex decoding is needed. However, it does not explicitly mention alternatives, exclusions, or conditions that would route an agent to a different sibling tool such as cyberchef_to_hex or cyberchef_magic.

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