Skip to main content
Glama
Sign In
THIRI Chord Intelligence — Music Theory MCP Server

THIRI Chord Intelligence — Music Theory MCP Server

by BluesPrince
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

conduct_band

Read-only

Generate a complete 4-piece band arrangement from a natural-language musical prompt. Returns tempo, groove, note lanes, lead sheet, and MIDI output.

Instructions

Arrange a 4-piece band from a natural-language prompt. Returns conductor tempo/groove, 4 lanes of note events, lead sheet, and base64 MIDI. Browser/client synthesizes audio via Csound; use thiri-conductor-mcp locally to render WAV.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "conduct_band"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesMusical direction (e.g. '12-second neo-soul band in Eb, Rhodes + analog bass')
durationSecNoOptional target duration override

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

Description adds value beyond annotations by specifying browser/client synthesis and local rendering path for WAV. Annotations already declare readOnlyHint=true, which is consistent as no external state is mutated.

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

Conciseness5/5

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

Two sentences, no wasted words, front-loaded with core purpose. Every sentence adds value.

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?

Describes outputs (tempo, lanes, lead sheet, MIDI) and synthesis context despite no output schema. For a complex creative tool, this is reasonably complete.

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 100%, baseline 3. Description adds meaningful example for prompt ('12-second neo-soul band in Eb...') and clarifies durationSec as optional override, enhancing understanding.

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

Purpose5/5

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

Specific verb 'Arrange a 4-piece band' with clear resource and outcome. Distinct from sibling chord-analysis tools.

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?

States output and local rendering requirement explicitly, providing context for use vs alternatives. No when-not-to-use guidance, but siblings are clearly different.

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