Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

hex_dump

Render text or bytes as a classic offset, hex and ASCII dump, with a mode to decode a dump back to text. Pure CPU, instant.

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": {
      "input": "<input>"
    },
    "name": "hex_dump"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesText or hex dump
reverseNoDecode a hex dump back to text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed3 schema fields changed
    • addedInput schema / properties / input
      Added value: +{
+  "description": "Text or hex dump",
+  "type": "string"
+}
    • addedInput schema / properties / reverse
      Added value: +{
+  "description": "Decode a hex dump back to text",
+  "type": "boolean"
+}
    • addedInput schema / required
      Added value: +[
+  "input"
+]
  4. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavior burden, and 'Pure CPU, instant' does add real value by signaling a local, side-effect-free, non-networked transformation. It stops short of describing error behavior for malformed input or a non-dump passed with reverse=true, which is the main residual risk for an agent.

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?

A single sentence with two clauses, front-loading the primary rendering behavior before the reverse mode. No filler, no repetition of the tool name.

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 trivial two-parameter pure function with no output schema, the description conveys the output shape (offset, hex, ASCII) and the cost profile, which is nearly everything an agent needs. The only gap is unspecified behavior on invalid input or a reverse decode of non-dump text.

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 100%, so both 'input' and 'reverse' are already documented in the schema; the description only restates that reverse decodes a dump back to text. It does add the nuance that 'input' accepts either raw text or bytes, but that is marginal beyond the schema (baseline 3).

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?

States a specific verb and output form: render text or bytes as an offset/hex/ASCII dump, plus a reverse decode mode. The named output format (offset + hex + ASCII columns) inherently separates it from sibling encoders like base64, base32, or hash, so an agent can pick it without opening the schema.

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 mention of a 'mode to decode a dump back to text' implies when the reverse path applies, but the description never explicitly says when to choose this over neighbors such as bytes_format, base64, or hash, nor any prerequisites. Usage is inferable but not stated.

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

All GadgetHumans API Hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources