messier-live

Overview Schema Source Related Servers Discussions Admin

Fx Pulse

fx_pulse

Punch a performance FX macro into a DJ deck for a set number of bars, then cut it to create glitch rolls, echo stabs, and granular washes. Set deck, macro, intensity, and bar count for bar-synced FX.

Instructions

Punch a PERF macro to intensity for N bars, then cut it — glitch rolls, echo stabs, one-bar granular washes.

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": {
      "deck": "<deck>",
      "macro": "<macro>"
    },
    "name": "fx_pulse"
  }
}

Input Schema

Name	Required	Description	Default
`bars`	No
`deck`	Yes
`macro`	Yes
`intensity`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal key behavior: the macro is applied for N bars and then cut off, indicating the effect is temporary. However, it does not clarify whether this mutates state, requires a loaded deck, affects current playback, or leaves any residual state behind.

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

Conciseness4/5

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

The description is a single concise sentence that front-loads the core action. The effect examples at the end add flavor but are not strictly necessary; despite that, nothing is redundant and the structure is easy to parse.

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 no annotations, no parameter descriptions, and an output schema whose contents are unknown, the description is not enough for confident invocation. It leaves required parameter semantics, usage context, and expected behavior gaps. It is adequate for understanding the general idea but not complete enough for reliable agent use.

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%, so the description must explain the parameters. It mentions 'intensity', 'N bars' (bars), and 'macro', but the required 'deck' parameter is entirely absent. It also provides no accepted value ranges or formats for macro or deck, leaving required parameters under-explained.

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 states a concrete action with a specific resource: 'Punch a PERF macro to intensity for N bars, then cut it.' It clearly communicates a transient macro pulse effect and includes evocative examples of the result. It is less than a 5 because 'PERF' is unexplained and the relationship to sibling tools like set_fx_macro is not explicitly distinguished.

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 guidance on when to use this tool versus alternatives such as set_fx_macro or fx_sweep. The description implies a performance-oriented effect but does not state conditions, prerequisites, or exclusion criteria. An agent must infer the appropriate context from the name and effect examples alone.

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