Skip to main content
Glama
Sign In
windy-word-mcp

windy-word-mcp

by sneakyfree
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

set_active_sound_pack

Switch the active sound pack for all hook stages. Choose from built-in packs like classic-beep or silent, or use custom pack IDs.

Instructions

Switch the active sound pack. Pack ids come from list_sound_effect_packs — typical built-ins are "_silent", "classic-beep", "soft-chime". Affects all 6 hook stages unless individually overridden via custom-sound assignments. Persisted via EffectsEngine _saveSettings.

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": {
      "packId": "<packId>"
    },
    "name": "set_active_sound_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
packIdYesPack id (e.g. "classic-beep", "_silent").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, but description discloses that the action persists via EffectsEngine _saveSettings and affects all 6 hook stages, giving useful behavioral context beyond the schema.

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?

Three concise sentences, front-loaded with purpose, no wasted words.

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 simple tool with 1 parameter and no output schema, the description fully covers purpose, parameter source, scope, and persistence.

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?

Only one parameter with 100% schema coverage; description adds examples of valid pack IDs and explains their source, supplementing the schema.

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?

Description clearly states 'Switch the active sound pack' (verb+resource) and provides context about pack IDs coming from list_sound_effect_packs, distinguishing it from sibling tools like list_sound_effect_packs and set_sound_hook.

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?

Provides guidance on where to find pack IDs (list_sound_effect_packs) and notes that it affects all hook stages unless overridden, implying when this tool is appropriate vs custom assignments.

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

Deploy Server

Other Tools