GMA2 MCP

set_effect_seconds

Set effect speed in seconds for precise timing control, offering an alternative to BPM or Hz settings.

Instructions

Set effect speed in seconds (alternative to BPM/Hz).

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": {
      "value": "<value>"
    },
    "name": "set_effect_seconds"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavior. It only states it sets effect speed, a write operation, but lacks details on range, validation, side effects, or success/failure outcomes. This is insufficient for safe invocation.

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

Conciseness3/5

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

Single sentence is concise but omits essential information. It achieves brevity at the cost of completeness. Could be restructured to include parameter details without being verbose.

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?

Given only one required parameter and no output schema description (though output schema exists), description lacks example, validation rules, or success indication. The tool's behavior is under-specified for reliable use.

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

Parameters1/5

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

Schema description coverage is 0%, yet description adds no meaning to the 'value' parameter. It does not specify unit (seconds), range, constraints, or typical values. The parameter is left completely unexplained.

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?

Description states clear verb 'Set', resource 'effect speed', and unit 'seconds', distinguishing it from sibling tools like set_effect_speed (likely BPM/Hz). It explicitly mentions being an alternative, clarifying its specific role.

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?

Mentions 'alternative to BPM/Hz' implying when to use seconds, but does not explicitly state when not to use or list alternatives like set_effect_speed. Provides directional guidance but not full exclusion criteria.

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

Deploy Server