pattern_delete
Delete a pattern by specifying its index to remove unwanted patterns from your FL Studio project.
Instructions
Delete a pattern by index.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| index | Yes |
Delete a pattern by specifying its index to remove unwanted patterns from your FL Studio project.
Delete a pattern by index.
| Name | Required | Description | Default |
|---|---|---|---|
| index | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only states 'Delete a pattern by index' without explaining permanence, consequences, or whether deletion is reversible. For a destructive operation, this is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise at 5 words, but at the cost of missing critical details. A deletion tool warrants more explanation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description is too sparse. It fails to explain the behavior or parameter meaning adequately, leaving the agent with minimal actionable information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'index' is described in the schema as a required integer but has 0% description coverage. The tool description says 'by index' but does not clarify indexing (e.g., zero-based vs one-based) or how to determine the index. Schema coverage is low, so the description fails to compensate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the verb 'Delete' and resource 'pattern' with the selection criterion 'by index'. Among sibling pattern tools, this uniquely identifies its deletion purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives (e.g., pattern_clear_step_sequence or other modifications) or any prerequisites. The description provides no usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Boyan253/fl-studio-2025-ai-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server