Skip to main content
Glama
Sign In
waveform-MCP

waveform-MCP

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

snapshot_recall

Restore a previously saved snapshot to make it the active edit in your audio project.

Instructions

Restore a previously-saved snapshot as the active Edit.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior1/5

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

No mention of side effects (e.g., whether restoring overwrites the current edit, whether it reverts unsaved changes, or if it is destructive). With no annotations, the description carries no behavioral information beyond the basic action.

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 a single, succinct sentence that conveys the core purpose without redundant words. It is appropriately minimal for the tool's simplicity.

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?

While the purpose is clear, the description omits critical context about the tool's behavior (e.g., what happens to the current edit, whether it is reversible) and does not provide any usage context. For a state-altering operation like restore, this leaves the agent underinformed.

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?

The only parameter 'name' has no description beyond its type (string). There is no explanation of what 'name' refers to (e.g., a snapshot identifier) or how it is used, leaving the schema effectively unusable without additional context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Restore') and the object ('a previously-saved snapshot') and ties it to the 'active Edit', which distinguishes it from snapshot save/list siblings. However, it does not explicitly reference sibling tools or further elaborate on the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like snapshot_save or snapshot_list. The description lacks any contextual cues for selection.

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