The Mechanical Ear
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 |
|---|---|
| list_tracksA | List all tracks in the Music For Robots catalog. Returns the catalog index: title, slug, duration for each track. Use the slug with get_track() or get_analysis() for full details. |
| get_trackA | Get the full manifest for a track by slug. Includes analysis data, timed review segments, full prose reviews, and YouTube URLs. The segments are synchronized to the audio — each observation was triggered by a specific moment in the track. Args: slug: Track slug from list_tracks (e.g. "pink-sky-at-night") |
| get_analysisA | Get only the analysis data for a track. Returns spectral, dynamics, harmonic, structural, rhythmic, and compression loss metrics. Useful for comparing tracks numerically. Args: slug: Track slug from list_tracks (e.g. "pink-sky-at-night") |
| search_reviewsA | Search across all review segments for a keyword or phrase. Searches both Vincent and Robach timed review segments. Returns matching segments with track title, critic, timestamp, and text. Args: query: Search term (case-insensitive) |
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_track and get_analysis overlap because get_track returns analysis data too, but descriptions clarify that get_analysis is a focused numeric endpoint. search_reviews is distinct from get_track's embedded review segments. Boundaries are mostly clear.
All tool names follow a consistent snake_case verb_noun pattern: list_tracks, get_track, get_analysis, search_reviews. No deviations or mixed conventions are present.
Four tools is well-scoped for a read-only catalog and review server. Each tool serves a clear purpose: index, full record retrieval, numeric analysis, and keyword search.
Covers listing, retrieval, analysis, and review search for the catalog. Minor gaps include no direct search/filter by track title or artist and no comparison aggregation, but list_tracks provides a workaround.