Skip to main content
Glama

Message a player

send_message

Send a private chat message to a specified online player by exact username. Use it for direct, one-to-one communication within the Minecraft server.

Instructions

Send a private chat message to one online 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>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesMessage text.
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.5/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive, non-open-world mutation. The description adds the useful constraint that the recipient must be currently online, which explains a likely failure mode. It does not say what happens when the player is offline or unknown, nor whether delivery is guaranteed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the recipient-type constraint comes before any other detail. Nothing is redundant, though the extreme brevity leaves no room for the behavioral caveats an agent might need.

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 two-parameter tool with full schema coverage, complete annotations, and an output schema that carries return details, the description covers the essentials. The remaining gap is failure behavior for offline or mistyped usernames, which matters given the explicit online requirement.

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 the schema already documents both parameters including the case-sensitive online-player constraint and the 1-4096 length bounds. The description repeats the online-player requirement rather than adding new meaning, so the baseline 3 applies.

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 names a specific verb and resource ('Send a private chat message') and constrains the target to 'one online player', which implicitly separates it from a broadcast tool. It does not name the closely related send_rich_message sibling, so the differentiation depends on the agent inferring it from 'private ... message'.

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?

'one online player' implies usage scope and implicitly excludes broadcast-style siblings such as broadcast_message. However, there is no explicit guidance on when to prefer send_rich_message (formatted content) over this plain-text variant, and no stated exclusions or preconditions beyond the online constraint.

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