Skip to main content
Glama
Sign In
waveform-MCP

waveform-MCP

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tempo_set

Set the global project tempo in beats per minute, accepting values from 20 to 200 for the current track.

Instructions

Set the project tempo in BPM (currently single global tempo; per-bar curves later).

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": {
      "bpm": "<bpm>"
    },
    "name": "tempo_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
bpmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

The description implies a mutating action on the project tempo but does not disclose side effects such as affecting playback, existing automation, or whether the change is undoable. With no annotations, more explicit behavioral detail would improve transparency.

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 very short, direct, and front-loads the action. The parenthetical scope note adds useful context without unnecessary verbosity.

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

Completeness5/5

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

For a simple one-parameter tool with no output schema, the description is complete enough: it states what the tool does, the unit of the parameter, and the current limitation. No additional context is needed.

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 only parameter, bpm, is explained as a tempo value in BPM and the schema already provides numeric constraints. Since schema descriptions are absent, the description compensates reasonably by naming the unit.

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?

Clearly states the action (set) and the target resource (project tempo) with the unit BPM. Also clarifies the current scope as a single global tempo, distinguishing it from future per-bar curves.

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?

Provides some usage context by noting that only a single global tempo is supported currently and per-bar curves are not yet available. It does not explicitly name alternative tools, but the scope note helps avoid misuse.

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