modularsynth-mcp

Overview Schema Source Related Servers Discussions Admin

List sounds

list_sounds

Read-only

List available sampler sounds, including built-in starter sounds and browser-saved user samples, then choose one to load with set_sample.

Instructions

List the sounds a sampler can play: the built-in starter kit (kick, snare, hi-hat, a chord, a pad — always available, made by the synth itself) and the user’s own sounds saved in this browser. Load one with set_sample.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sounds"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1Nov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the built-in kit is always available and synthesized by the tool itself, while the user's sounds live in this browser — useful for reasoning about persistence and emptiness.

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?

A single well-formed sentence that front-loads the resource and folds the category breakdown and the follow-up action into the same line with no filler.

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 zero-param, read-only listing tool with no output schema, the description supplies everything needed: what is returned, where the two sound sources come from, and the natural next call. No output schema exists, so describing the return contents in prose is appropriate.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is trivially complete with additionalProperties=false.

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?

States a specific verb and resource ("List the sounds a sampler can play") and enumerates the two categories returned: the built-in starter kit and the user's browser-saved sounds. This is clearly distinct from sibling listing tools such as list_presets and list_module_types, which cover different resource types.

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?

Explicitly routes the agent forward: "Load one with set_sample," telling it this is a discovery step that precedes sample selection. It does not state when to prefer this over list_presets, but the resource scope makes the distinction largely self-evident.

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