GMA2 MCP

create_macro

Store an empty macro, then assign command strings to sequential lines. Optionally label the macro for organization.

Instructions

Create a macro with command lines.

Stores an empty macro, then assigns each command to sequential lines.
Optionally labels the macro.

Args:
    macro_id: Macro number to create
    commands: List of command strings for each macro line
    name: Optional label for the macro
    pool: Macro pool number (default: 1)

Returns:
    str: Operation result message

Examples:
    - Create macro 10 with commands ["Go Sequence 1", "Go Sequence 2"]
    - Create macro 10 named "Start Show" with one command

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>",
      "commands": "<commands>"
    },
    "name": "create_macro"
  }
}

Input Schema

Name	Required	Description	Default
`macro_id`	Yes
`commands`	Yes
`name`	No
`pool`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description explains that it first stores an empty macro then assigns commands to sequential lines, optionally labels, and uses a default pool. It also states the return type. No annotations are present, so the description carries the full burden and does well.

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?

The description is succinct: a one-line intro, followed by structured Args and Returns sections, then two examples. Every sentence adds value; no fluff.

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?

The description covers the creation process, parameter details, and return type. With an output schema present, the return value is sufficiently described. Missing are error conditions and behavior if macro_id already exists, but overall it is fairly complete for this tool.

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?

Despite 0% schema coverage, the description lists all four parameters (macro_id, commands, name, pool) with brief explanations and examples. This adds meaning beyond the raw schema, though some constraints (e.g., valid macro_id range) are missing.

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 'Create a macro with command lines' and explains the process of storing an empty macro and assigning commands sequentially. This distinguishes it from sibling tools like set_macro_line or run_macro.

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?

While the purpose is clear, there is no explicit guidance on when to use this tool versus alternatives (e.g., set_macro_line for modifying existing macros, label_macro_tool for labeling). The description does not provide 'when to use' or 'when not to use' context.

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

Deploy Server