hackyeaster-solver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| he_discover_challengesB | Scrape hackyeaster.com and return a list of available challenges with titles, URLs, descriptions, and embedded data. |
| he_fetch_challengeA | Fetch a specific challenge page and return parsed content: title, description, hints, code blocks, images, links. |
| he_fetch_rawC | Fetch any URL and return the raw HTML. Useful for following links or checking resources. |
| he_decodeB | Decode data using a specified encoding: base64, hex, url, binary, morse, decimal, octal, base32. |
| he_transformB | Apply a cipher/transform: caesar (with shift param), rot13, swap_pairs, reverse, rail_fence (with rails param), vigenere (with key param), xor (with key param), atbash, caesar_bruteforce. |
| he_analyze_imageA | Download an image URL and return it as base64 for visual analysis. Also attempts QR code / barcode detection if pyzbar is available. |
| he_hashB | Compute a hash of the given data. Algorithms: md5, sha1, sha256, sha512. |
| he_log_attemptB | Record a solve attempt for a challenge. Tracks answer, correctness, and notes. |
| he_get_progressA | Return all solve attempts grouped by challenge, with summary of total attempts and solved count. |
| he_validate_flagA | Check if a string matches the HackyEaster flag format (he20XX{...}). |
| he_submit_flagA | Submit a flag for a challenge via the authenticated HackyEaster API. POSTs to /app/rest/user/challenge/{id}/checkflag. Returns the API response (accepted/rejected/already-solved). |
| he_download_fileA | Download a challenge's attached file via the authenticated HackyEaster API. Fetches /app/rest/user/challenge/{id}/file and saves to the data/ directory. Returns the saved path, filename, content-type, and size in bytes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a distinct purpose: image analysis, hashing, logging, progress tracking, flag handling, file download, challenge discovery, page fetching, raw HTML fetching, decoding, and transformation. No overlapping functionality.
All tools use the 'he_' prefix and snake_case. Most follow verb_noun pattern (e.g., analyze_image, validate_flag) with a few single-verb names (hash, decode, transform) that are clear in context.
12 tools cover all necessary operations for the HackyEaster puzzle solver domain: discovery, fetching, analysis, decryption/transformation, flag submission, and progress tracking. Neither too sparse nor too many.
The toolset covers core workflows well, including image analysis with QR/barcode detection, hashing, decoding, cipher transformations, and flag lifecycle. Minor gaps like encoding or OCR are not essential for the domain.