house-mcp
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_songA | Analyze a reference audio file (.mp3/.wav). Returns tempo (BPM, house-folded), best key guess + candidates, an approximate 2-chord vamp, and an 8-section energy structure map. Use this first when matching a reference track's vibe. |
| generate_arrangementA | Generate a house MIDI pack (separate .mid per instrument) into out_dir. bpm: tempo, 60 to 200. root: key root note like 'G','A','C#'. mode: 'minor' or 'major' (sets the i-chord quality; the vamp is i7 + ii-m7 a whole step up). arrangement: 'loop' (8-bar groove) or 'full' (128-bar, 8 sections: intro/groove/breakdown/build/drop/breakdown/groove/outro). Drums use GM notes (kick=36, clap=39, snare=38, closed hat=42, open hat=46). Pitched parts need a synth per channel. Returns the list of written files. |
| list_packB | List the .mid files in a generated pack folder with sizes. |
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 3 tools
Each tool has a clearly distinct purpose: analyze_song reads audio, generate_arrangement writes MIDI, list_pack inspects output folders. No overlap in resource or action, so misselection is unlikely.
All three tools follow a consistent snake_case verb_noun pattern: analyze_song, generate_arrangement, list_pack. Tense and style are uniform throughout.
Three tools is on the thin side but fits a narrow analyze→generate→inspect workflow without bloat. Each tool earns its place, though one or two more (e.g. regenerate/validate) would round it out.
Core happy path (analyze reference → generate pack → list files) is covered, but the surface has dead ends: no delete/cleanup, no inspecting individual .mid contents, and no way to modify or regenerate a section of an existing arrangement.