Skip to main content
Glama
ismail: agent DAW (MCP server)

ismail: agent DAW (MCP server)

Live Control

live_control

Move a mapped DAW control to a value (0–1 or raw units), applying changes immediately and logging them; values at or above 0.5 can fire the mapped action.

Instructions

Move a mapped control (what the stage sends when a knob turns; an agent can turn one too, the same way). value: 0..1, or the param's own units for a 'raw' map. Applies at once and is logged with its bar. A map with an action fires it on 0.5 or more; the reply is the action's.

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": {
      "project": "<project>",
      "control": "<control>",
      "value": "<value>"
    },
    "name": "live_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
controlYes
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose real behavior: the change applies immediately, is logged against its bar, and a map with an action fires at value >= 0.5 with the action's reply returned. It omits whether the write is reversible/undoable, whether an unmapped control errors, and whether project scope implies permissions or isolation.

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?

Short and free of filler, but the writing is telegraphic and the parenthetical 'what the stage sends when a knob turns' precedes the actual semantics, so the front-loaded portion is the least informative part. The threshold and reply behavior are buried mid-sentence rather than surfaced.

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?

An output schema exists, so return values need not be spelled out, but for a 3-required-parameter mutation tool with no annotations and zero schema coverage the description leaves too much open: how to obtain a valid control name, what project scopes, and what failure modes look like. It is not sufficient for an agent to call this correctly without trial and error.

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

Parameters2/5

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

Schema description coverage is 0% across three required parameters. The description only explains 'value' partially (0..1, or the param's own units for a 'raw' map) and leaves 'control' as an implied identifier with no naming/format guidance, and never mentions 'project' at all, so two of three parameters remain undocumented anywhere.

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

Purpose3/5

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

States a verb and object ('Move a mapped control') and clarifies via parenthetical that this is the same thing the stage sends when a knob turns, so an agent can infer it writes a value to a mapped parameter. However 'mapped control' is unexplained jargon and the description never distinguishes this from siblings like live_map, live_controls, stage_control_set, or stage_control_map, which appear to touch the same domain.

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?

There is no explicit when-to-use guidance and no named alternative. The reader must guess whether mapping must be established first (live_map), whether live_controls should be consulted to discover a control name, or how this differs from stage_control_set. Only the action-threshold rule hints at a usage condition.

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