Skip to main content
Glama
williamzujkowski

Strudel MCP Server

by williamzujkowski
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

remove_effect

Remove audio effects from Strudel music patterns to modify sound characteristics or clean up compositions.

Instructions

Remove effect

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
effectYesEffect to remove

Implementation Reference

  • src/server/EnhancedMCPServerFixed.ts:317-327 (registration)
    Registration of the 'remove_effect' tool in getTools(), including its input schema. No separate handler implementation found in the switch statement of executeTool.
    {
  name: 'remove_effect',
  description: 'Remove effect',
  inputSchema: {
    type: 'object',
    properties: {
      effect: { type: 'string', description: 'Effect to remove' }
    },
    required: ['effect']
  }
},

Tool Definition Quality

C2.1/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Remove effect' implies a destructive mutation, but the description doesn't specify whether removal is permanent, reversible (e.g., via 'undo'), requires specific permissions, or has side effects. It lacks critical context about what 'remove' actually does operationally.

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?

The description is extremely concise with just two words, 'Remove effect', which directly states the action and target. There is no wasted verbiage or unnecessary elaboration, making it front-loaded and efficient, though this brevity contributes to other deficiencies in clarity and completeness.

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 the lack of annotations and output schema, and the tool's likely destructive nature (implied by 'remove'), the description is incomplete. It doesn't address what happens post-removal, error conditions, or return values. For a mutation tool with no structured support, more descriptive context is needed to guide safe and correct usage.

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 description coverage is 100%, with the single parameter 'effect' documented as 'Effect to remove'. The description adds no additional meaning beyond this schema, as it doesn't clarify what constitutes an 'effect' (e.g., audio effect, visual effect, named preset) or provide examples. Baseline 3 is appropriate since the schema handles parameter documentation adequately.

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

Purpose2/5

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

The description 'Remove effect' is a tautology that restates the tool name without adding meaningful context. It specifies the verb 'remove' and resource 'effect', but doesn't explain what an 'effect' is in this context or what removal entails. Compared to sibling tools like 'add_effect' or 'clear', it doesn't distinguish its specific scope or behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether an effect must exist first), exclusions, or relationships to siblings like 'add_effect' or 'clear'. Without any usage context, an agent cannot determine appropriate invocation scenarios.

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/williamzujkowski/strudel-mcp-server'

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