Ruin Everything
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUIN_AUTO_UPDATE | No | Set to 0 to manage versions yourself and disable automatic background update checks. | |
| RUIN_RULE_UPDATES | No | Set to 0 to use the bundled site selector rules instead of fetching rule updates. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ruin_auto_registerB | Handle an open Workday Sign In or Create Account dialog at the exact job URL, or fill a supported signup form. Credentials come from the local profile. |
| inspect_application_challengeA | Inspect the original Greenhouse or Ashby application tab at its exact job URL. Use when Greenhouse asks for an 8-character email security code, including reports of '[one-time authentication code withheld]', or Ashby displays a reCAPTCHA image grid. On a lost tab, report whether the shared local browser still has it. Return the visible state only. Mailbox contents, CAPTCHA solving, Duo 2FA, PayPal Security Challenge and payment actions are outside this tool's scope. A positive wait watches just this job. |
| get_ashby_receiptA | Check the exact Ashby job first when asked whether it was submitted, including at handoff or after a lost tab. A stored receipt confirms success even with Chrome closed. Unrecorded means the outcome is unknown. |
| watch_ashby_receiptB | Watch the original Ashby form when a challenge clears or a submitted application has no receipt yet. Return saved evidence or record the official success message for this job. This never submits the form. |
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 4 tools
get_ashby_receipt and watch_ashby_receipt both concern Ashby submission receipts and could be confused at selection time, though one is an immediate lookup and the other a waiting watcher. inspect_application_challenge also partially overlaps with the receipt tools since it deals with Ashby challenge state, and coverage is split oddly across platforms.
All names are snake_case with a verb-first pattern (auto_register, inspect, get, watch), which is readable and consistent. The stray 'ruin_' prefix on only one tool is a minor deviation from the otherwise uniform convention.
Four tools is a tight, well-scoped set for a narrow challenge-handling workflow, with each tool earning a distinct role. It is slightly thin given the tool set references three platforms (Workday, Greenhouse, Ashby).
Challenge inspection and Workday dialog handling are covered, but receipt/status verification exists only for Ashby, leaving Workday and Greenhouse submissions without any outcome-checking tool. This is a notable gap in lifecycle coverage across the stated platforms.