Skip to main content
Glama

Play sound

play_sound

Plays a sound for a specific online Minecraft player at their location or exact coordinates, with control over volume, pitch, and sound category.

Instructions

Play a sound to one online player, at a position or (by default) at the player.

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>",
      "sound": "<sound>"
    },
    "name": "play_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoExact X; give x, y and z together or leave all out.
yNoExact Y; give x, y and z together or leave all out.
zNoExact Z; give x, y and z together or leave all out.
pitchNoPlayback speed/pitch, 0.5-2.
soundYesSound event such as 'entity.experience_orb.pickup' or 'block.note_block.harp'.
sourceNoVolume slider category the sound uses.master
volumeNoVolume; above 1 mainly extends the hearing range.
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.8/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description still adds real behavior the schema does not state: if coordinates are omitted, the sound plays at the player rather than at a world position. It does not mention hearing range or that only the named player receives it beyond 'one online player'.

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 sentence with the resource first and the default-target behavior parenthetically front-loaded. Nothing is redundant, and no sentence is wasted.

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?

Eight parameters are all documented in the schema, and an output schema exists so return values need no explanation. The description covers the non-obvious default targeting, but for a sound tool it omits practical details such as audible range or what happens if the player is offline.

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%, so pitch, volume, source, and the x/y/z all-or-nothing rule are already documented. The description only reinforces the position-vs-default distinction and adds no semantics for the remaining parameters, which matches the baseline of 3.

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?

States a specific verb and resource ('Play a sound'), the audience constraint ('to one online player'), and the targeting mode ('at a position or by default at the player'). That is enough to separate it from stop_sound, though it never names that sibling explicitly.

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?

Usage is only implied: the agent can infer a player must be online and coordinates are optional, but there is no statement of when to prefer this over related tools like stop_sound or broadcast_message, and no prerequisites or failure conditions are given.

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