Guitar Tone Assistant
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TONE3000_SECRET_KEY | No | Your TONE3000 secret API key. Required for live TONE3000 tools; without it, local AmpliTube tools still work but TONE3000 tools return configuration errors. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tone3000A | Search authenticated TONE3000 tone packs and rank results for an amp family, style, artist, song, tags, and required capture type. Returns direct tone-page links, not model downloads. |
| get_tone3000_toneA | Resolve a TONE3000 tone ID or URL, classify its captured stages, and list its models and authenticated model download URLs. |
| search_tone3000_cabsA | Find TONE3000 cabinet/IR tone packs by speaker, cabinet size, and tonal character. Returns direct tone-page links. |
| search_amplitube_gearA | Search the bundled, curated AmpliTube 5 MAX knowledge layer by gear type, amp family, gain level, or style. Mapping confidence is included so uncertain product identities are not presented as fact. |
| recommend_tone_chainB | Build a practical TONE3000-focused, AmpliTube-only, or hybrid rig with capture-aware routing, starting settings, cab advice, gain staging, and live TONE3000 candidates when configured. |
| troubleshoot_toneA | Return prioritized, exact changes for fizzy, muddy, thin, harsh, boomy, over-compressed, or slow/soft attack problems while checking for accidental double-cab routing. |
| compare_tonesA | Compare two to four TONE3000 tone packs by gain clues, EQ clues, cab requirements, flexibility, and likely use. Uses metadata conservatively and returns direct links. |
| get_user_tone_profileA | Read an optional local profile containing guitars, pickups, tunings, interface, favorite amps/IRs, and monitoring device. |
| save_user_tone_profileA | Replace an optional local tone profile. This writes only to the server's local profile store and never sends profile data to TONE3000. |
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 9 tools
Every tool targets a distinct operation: searching tone packs, cabs, or AmpliTube gear; resolving a specific TONE3000 tone; recommending; troubleshooting; comparing; and managing user profile. Although several tools start with 'search', their resource/noun suffixes and descriptions make misselection unlikely.
All tool names use snake_case and a consistent verb-first pattern: search_*, get_*, save_*, recommend_*, troubleshoot_*, and compare_*. The naming is predictable and readable even when targets are compound nouns like tone3000_tone or tone_chain.
Nine tools is solidly in the well-scoped range for an assistant server of this type. Each tool—search, resolution, cab search, AmpliTube search, recommendation, troubleshooting, comparison, and profile read/write—earns its place without bloat.
The set covers the full assistant workflow: searching TONE3000 tones and cabs, searching AmpliTube gear, resolving tone details and model URLs, recommending rigs, troubleshooting problems, comparing tones, and reading/writing user profile context. There are no dead ends; TONE3000 candidates flow from search/recommend/get into comparison and download-URL access.