Skip to main content
Glama

music_styles

Lists music styles or returns a style’s defining tempo, meter, scales, harmony, rhythm, bass, melody, arrangement, and Live device guidance for composing or rearranging tracks.

Instructions

Style sheets for composing or re-arranging: without style, the list; with it, what makes the style: tempo, metre, scales/modes, harmonic language, typical progressions (roman numerals for write_progression), rhythm/groove and swing amount, bass, melody, arrangement, accompaniment patterns, and which Live devices/tools help. Styles: baroque, classical_romantic, jazz, bossa_nova, blues, gospel_neo_soul, funk, pop, rock, house, techno, trance, drum_and_bass, hip_hop_boom_bap, lofi, trap, rnb, reggae, reggaeton, afrobeat, flamenco, film_epic, ambient, synthwave (aliases such as "Bach", "lo-fi", "dnb" work).

Parameters:

  • style: Style name (optional)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "music_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the full burden and does well: it discloses the two response modes, enumerates the categories of content returned in detail mode, and states that aliases are accepted. It omits error behavior for an unrecognized style name, which is the main remaining gap for a lookup tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The dual-mode rule is front-loaded and the long style enumeration earns its space given the schema has no enum. The mid-sentence list of returned attributes is dense comma-separated prose that slows parsing slightly, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter lookup tool with an output schema already covering return values, the description supplies the mode behavior, the valid value set, and alias handling. An agent has enough to invoke it correctly; only failure semantics for invalid styles are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema only declares a bare optional string, so the description must compensate — and it does, listing all 24 valid style values, noting that aliases like 'Bach', 'lo-fi', and 'dnb' resolve, and explaining that omitting the parameter returns the catalog. Only the unknown-value behavior is left unspecified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and dual behavior: without `style` it returns the list of styles, with `style` it returns that style's compositional attributes (tempo, metre, scales, progressions, groove, arrangement, devices). It reads clearly as a reference/lookup tool and even cross-references write_progression, though it never explicitly says how it differs from siblings like music_scales or music_chord_ideas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'without `style` ... with it ...' construction gives concrete conditional guidance for both call modes, and the framing 'for composing or re-arranging' sets the use context. It stops short of when-not-to-use guidance or naming alternative tools for overlapping needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools