Skip to main content
Glama

set_effect_form

Set the waveform form of the current effect selection. Accepts waveform type as name (e.g., 'sin') or number (e.g., 6).

Instructions

Set the effect waveform for the current selection.

Args:
    form: Waveform type — name (e.g., "sin", "ramp", "square") or number

Returns:
    str: Operation result message

Examples:
    - Set effect form to "sin"
    - Set effect form to 6

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided. The description discloses the action and examples but does not explain behavioral traits such as prerequisites (e.g., requires a selection), idempotency, side effects, or error conditions.

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?

Extremely concise: one action sentence, a clear Args section, a Returns note, and examples. No redundant or verbose content.

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

Completeness3/5

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

Adequate for a simple setter with one parameter. However, lacks context about how this tool fits into the broader effect system, return value details, or prerequisites, given no annotations.

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?

The description adds value by specifying the 'form' parameter accepts waveform names (e.g., 'sin', 'ramp') or numbers, providing examples beyond the schema's simple type string.

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 'Set the effect waveform' and specifies the scope 'for the current selection', distinguishing it from sibling tools like set_effect_speed or set_effect_phase.

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?

No explicit guidance on when to use this tool versus alternatives like set_effect_envelope or apply_effect. The sibling list implies this is for waveform type, but lacks when-to/when-not context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chienchuanw/gma2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server