Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

conversion_hamming_code

Read-onlyIdempotent

Encode binary data into a Hamming error-correcting codeword or decode a codeword to detect and correct single-bit errors. Returns syndrome, error position, and corrected codeword.

Instructions

Hamming Code Encoder and Decoder. Encode binary data into a Hamming error-correcting codeword or decode a codeword to detect and correct a single-bit error. In encode mode it inserts parity bits at power-of-two positions; in decode mode it computes the syndrome to locate and flip one flipped bit (Hamming distance 3: corrects 1-bit errors, detects up to 2-bit errors). Use it for error-correction coding demos and parity analysis; use conversion_parity_bit for a single even/odd parity bit, or conversion_gray_code for reflected-binary encoding. Runs locally on the bit string you provide: read-only, non-destructive, offline, and rate-limited (60 requests/min anonymous). Returns the codeword or recovered data bits plus the syndrome, error position, corrected codeword, and step-by-step working.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes"encode" turns data bits into a codeword; "decode" checks a codeword and corrects a single-bit error.
inputYesBinary string (0/1 only). For encode its length must equal the type's data bits (4/11/26); for decode it must equal the total bits (7/15/31).
hammingTypeNoCode size: hamming-7-4 (4 data/3 parity), hamming-15-11 (11 data/4 parity), hamming-31-26 (26 data/5 parity).hamming-7-4

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the operation succeeded.
resultNoEncode and decode share input, mode, hammingType, output, steps, explanation, properties; the remaining fields depend on mode.
Behavior5/5

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

Describes the encoding/decoding process (inserts parity bits, computes syndrome, flips bit) and return values (codeword, syndrome, error position, etc.). Aligns with annotations (readOnlyHint=true, destructiveHint=false) and adds rate limit info. No contradiction.

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?

Description is informative but slightly verbose; could be tightened. However, it is well-structured with purpose, mechanism, and usage notes in a logical order.

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

Completeness5/5

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

Covers all essential aspects: purpose, parameters, behavior, return values (output schema exists), constraints, and sibling differentiation. No gaps for a tool of moderate complexity.

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

Parameters5/5

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

Schema coverage is 100%, but description adds meaningful context: explains mode options, input length constraints per mode and hammingType, and examples of valid inputs. This goes beyond schema descriptions.

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?

Description clearly states it encodes binary data into Hamming codewords and decodes codewords to detect/correct errors. It distinguishes from sibling tools like conversion_parity_bit and conversion_gray_code by specifying alternative uses.

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

Usage Guidelines5/5

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

Explicitly says when to use this tool ('for error-correction coding demos and parity analysis') and when to use alternatives ('use conversion_parity_bit for a single parity bit, or conversion_gray_code for reflected-binary encoding'). Also notes local, read-only, offline, and rate-limited constraints.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server