Skip to main content
Glama
Sign In
hackyeaster-solver

hackyeaster-solver

by cloudwarriors-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

he_decode

Decode data encoded in base64, hex, URL, binary, Morse, decimal, octal, or base32 to retrieve the original content.

Instructions

Decode data using a specified encoding: base64, hex, url, binary, morse, decimal, octal, base32.

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": {
      "data": "<data>",
      "encoding": "<encoding>"
    },
    "name": "he_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe data to decode
encodingYesEncoding type: base64, hex, url, binary, morse, decimal, octal, base32

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, and description does not disclose error handling, return format, or side effects; only states core decode function.

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?

Single sentence with all essential information, front-loaded with action verb, no fluff.

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?

Simple tool with clear purpose, but missing usage guidance and behavioral details; adequate but not comprehensive given sibling overlaps.

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 covers both parameters fully (100% coverage), and description merely repeats the encoding list without adding new constraints or format details.

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 clearly states the tool decodes data using specified encodings, listing all options, and distinguishes from sibling tools like he_hash and he_transform which handle different operations.

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?

No guidance on when to use this tool versus alternatives such as he_transform; missing when-not-to-use or prerequisites.

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