Skip to main content
Glama
Sign In
GMA2 MCP

GMA2 MCP

by chienchuanw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

flash_executor

Bump an executor's intensity for live busking. Supports momentary flash, latching flash_on, or flash_go mode.

Instructions

Flash an executor (momentary intensity bump) — a live busking control.

Args:
    executor_id: Executor number
    page: Optional page number for page-qualified addressing
    mode: "flash" (momentary), "flash_on" (latching), or "flash_go" (flash and go)

Returns:
    str: Operation result message

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": {
      "executor_id": "<executor_id>"
    },
    "name": "flash_executor"
  }
}

Input Schema

NameRequiredDescriptionDefault
executor_idYes
pageNo
modeNoflash

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The description explains the three modes (flash, flash_on, flash_go) and mentions 'momentary intensity bump', but does not detail state changes, whether the executor returns to previous level, or any side effects.

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 extremely concise: a one-line summary followed by a clean Args and Returns section. Every sentence is necessary and well-structured.

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 tool's complexity (3 params, 1 required, output schema exists), the description covers the key parameters and behavior. It lacks information on prerequisites or error conditions but is adequate for a live control 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?

With 0% schema description coverage, the description's Args section adds necessary meaning: executor_id is 'Executor number', page gets 'Optional page number for page-qualified addressing', and mode lists the three options. This compensates well for the schema gaps.

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 action (flash) and resource (executor), and explains it's a 'live busking control', distinguishing it from other executor manipulation tools like set_executor_fader or release_executor.

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 explicit guidance on when to use this tool versus alternatives like stomp_executor, swop_executor, or temp_executor. The phrase 'live busking control' implies usage context but does not provide comparative decision criteria.

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