Skip to main content
Glama

Create probabilistic sequencer

create_prob_sequencer

Build a Markov-chain step sequencer that transitions between states on each beat, outputting state and trigger channels for probabilistic rhythm generation.

Instructions

Build a Markov-chain step sequencer. On each beat boundary the COMP transitions from the current state to a next state sampled from the per-state weighted-transition table. Outputs two CHOP channels: 'state' (current state index) and 'trigger' (pulse on state change). Generative sibling of create_euclidean_sequencer and create_beat_grid_sequencer — great for evolving, probabilistic rhythms and generative state machines. NOTE: beat-callback timing requires a live TD session with time.play=1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoContainer COMP name.prob_seq
parent_pathNoParent COMP path./project1
bpmNoTempo written to Beat CHOP when no bpm_source is provided.
divisionNoBeat subdivision (1/4→1, 1/8→2, 1/16→4 beats-per-measure).1/8
statesYesMarkov states. Each state has a unique id, a weight (initial distribution), and a transitions map (keys = state ids, values ≥ 0).
startStateNoInitial state id. If omitted, sampled from state weights.
bpm_sourceNoPath to an existing Beat CHOP / tempo source. Omit to build a new one.
seedNoIf set, seeds Python random for reproducible runs.
Behavior4/5

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

Annotations indicate it is not read-only or destructive. The description adds detailed behavioral context: state transitions, CHOP outputs, and the live session requirement. No contradictions found.

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?

Every sentence adds value without waste. The purpose is front-loaded, and the structure is logical: what, how, outputs, comparison, note.

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

Completeness4/5

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

Given 8 parameters with full schema coverage and no output schema, the description explains the core algorithm and outputs. It could mention the resulting network structure, but is adequate for the complexity.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions, which are already provided.

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 it builds a Markov-chain step sequencer with specific transition behavior and outputs, and distinguishes itself from siblings create_euclidean_sequencer and create_beat_grid_sequencer.

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?

It provides clear context for use (probabilistic rhythms, generative state machines) and mentions a prerequisite (live TD session with time.play=1), but doesn't explicitly exclude use cases where siblings would be better.

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/Pantani/tdmcp'

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