GMA2 MCP

setup_song_macro

Create a macro to store the current song name in a variable, enabling song tracking during music shows.

Instructions

Create a macro that sets a user variable to the song name.

Stores a macro, labels it with the song name, and assigns a SetVar
command on line 1. This is used to track the current song in
music show workflows.

Args:
    macro_id: Macro number to create
    song_name: Song name used for label and variable value
    var_name: Variable name for the SetVar command (default: "$song")

Returns:
    str: Operation result message

Examples:
    - Create macro 101 that sets $song to "Opening+Childhood"

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": {
      "macro_id": "<macro_id>",
      "song_name": "<song_name>"
    },
    "name": "setup_song_macro"
  }
}

Input Schema

Name	Required	Default
`macro_id`	Yes
`song_name`	Yes
`var_name`	No	$song

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It explains that it stores a macro, labels it, and assigns a SetVar command on line 1, but does not address idempotency, permissions, side effects (e.g., overwriting existing macros), or error scenarios.

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 well-structured with clear sections (purpose, details, args, returns, examples) and is not unnecessarily verbose. Minor redundancy could be trimmed, but overall it is efficient.

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?

Given the presence of an output schema (returning a string) and the description's coverage of arguments and return value, the tool is well-documented. It lacks details on error conditions or prerequisites (e.g., valid macro_id range), but these are minor omissions for a straightforward tool.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description includes a full docstring with Args and examples for all three parameters, explaining their roles, defaults, and usage. This fully compensates for the absence of schema descriptions.

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?

The description clearly states the verb 'Create' and the resource 'macro' with a specific purpose: setting a user variable to the song name. It distinguishes from sibling tools like 'create_macro' and 'set_user_variable' by detailing the combined action.

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

Usage Guidelines3/5

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

The description mentions it is used 'to track the current song in music show workflows,' providing context, but it does not explicitly state when not to use it or suggest alternatives like 'create_macro' for generic macros or 'set_user_variable' for direct variable setting.

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

Deploy Server