AIGigLab MCP Server

create_composition_plan

Generate a structured music composition plan from a text prompt, specifying style and optional duration.

Instructions

Create a composition plan for music generation.

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": "create_composition_plan"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes	Prompt to create a composition plan for (e.g., 'A synthwave track with a driving bassline')
`music_length_ms`	No	The length of the composition plan to generate in milliseconds (10000ms - 300000ms).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Jul 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the basic action. It fails to mention any side effects, idempotency, required permissions, or whether the plan is saved or ephemeral, leaving critical behavioral traits unspecified.

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 description is a single concise sentence that front-loads the action. However, it is overly brief and could be expanded to include more context without sacrificing conciseness.

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

Completeness2/5

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

The description is incomplete for an agent to fully understand the tool's role. It does not explain what a composition plan is, how it relates to other tools like 'compose_music', or what happens after creation. Given the lack of output schema and rich annotations, the description should provide more contextual details.

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

Parameters3/5

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

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The tool description itself adds no parameter-specific information; it relies entirely on the schema. While the schema provides adequate details, the description does not enhance understanding beyond the schema.

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 clearly states the verb 'create' and the resource 'composition plan for music generation', indicating the tool's core function. However, it does not differentiate from the sibling tool 'compose_music', which may also generate music-related output, leading to potential confusion for an agent.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'compose_music'. There is no mention of prerequisites, exclusions, or context that would help an agent decide which tool to invoke.

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