Skip to main content
Glama

Stop sounds

stop_sound
Idempotent

Stop sounds playing for an online player, either a single sound, a sound category, or everything at once. Use it to silence unwanted audio on a Minecraft server.

Instructions

Stop sounds playing for an online player: one sound, or everything.

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": {
      "username": "<username>"
    },
    "name": "stop_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
soundNoSound to stop; omit (with source) to stop every sound.
sourceNoOnly stop the sound in this category.
usernameYesExact, case-sensitive name of an online player.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering the safety and repeat-call profile. The description adds the online-player requirement and the one-sound-or-everything mode, but it does not explain what happens when the sound is not playing or whether stopping all has side effects.

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 a single front-loaded sentence with no wasted wording. The scope and the one-sound-or-everything distinction are stated immediately.

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?

For a simple three-parameter mutation with full schema coverage, annotations, and an output schema, the description is largely sufficient. It leaves some combination behavior and failure cases to the schema, which is reasonable for this tool.

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%, and every parameter already has a description and default, so the schema carries the parameter semantics. The description restates the one-sound-or-everything mode but adds no syntax, category interaction, or precedence details beyond the schema.

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

Purpose4/5

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

The description uses a specific verb ('Stop') and resource ('sounds') and scopes it to an online player, with a clear one-sound-or-everything distinction. It does not explicitly name a sibling alternative, so it stops short of full differentiation.

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

Usage Guidelines3/5

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

The description implies this tool is for stopping active sounds for an online player, but it gives no explicit when-to-use conditions, prerequisites, or comparison to alternatives such as play_sound. The one-vs-everything mode is mentioned without guidance on choosing between them.

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