Skip to main content
Glama

Message players

send_message

Send chat messages, titles, or action bar text to chosen Minecraft players or everyone online, with an optional sound for named players.

Instructions

Send a chat message, title, or action bar text to some players, or to everyone online when players is left out. A sound plays only for named players, who must be online.

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": {
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhere it showschat
soundNoSuch as `minecraft:entity.experience_orb.pickup`
formatNo`minimessage` reads tags like `<green>Hi` or `<bold>`; `plain` sends the text as isplain
messageYesThe text
playersNoNames or UUIDs; everyone online when left out
subtitleNoOnly for titles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.2.1
    • addedInput schema / properties / kind / description
      Added value: +"Where it shows"
    • addedInput schema / properties / message / description
      Added value: +"The text"
  2. First observedv4.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (not read-only, not destructive, not idempotent, closed-world). The description adds one real behavioral fact beyond that: a sound only plays for explicitly named players and those players must be online. It leaves open what happens with an offline or unknown player name, and whether sending is rate-limited or permissioned.

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?

Two front-loaded sentences with no filler: the action and target scope come first, then the one non-obvious caveat about sounds and online players. Nothing to trim.

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?

With no output schema and six well-documented parameters, the description supplies the target-scope and sound prerequisites an agent needs before calling. Only edge-case behavior (unknown/offline names, permission failures) is unaddressed.

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%, so every parameter including kind, format, and players is already documented in the schema, including the 'everyone online when left out' default. The description re-states that players rule and adds the sound/named-players constraint, giving value but not much beyond structured fields — baseline 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 plus the three output surfaces (chat message, title, action bar text), so the agent knows exactly what the tool produces. It does not explicitly distinguish itself from close siblings like run_command or manage_webhook, which keeps it short of a 5.

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?

'To everyone online when players is left out' implies the broadcast usage case, but the description never says when to prefer this over run_command or a webhook, nor any prerequisite such as permission to message players. Usage is inferable rather than stated.

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