Skip to main content
Glama

Send formatted message

send_rich_message

Sends formatted Minecraft chat messages with colors, clickable text, and hover details to a player or selector using vanilla /tellraw.

Instructions

Send a formatted (coloured, clickable, hoverable) chat message using vanilla /tellraw.

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": {
      "target": "<target>",
      "text": "<text>"
    },
    "name": "send_rich_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesRaw JSON text component, e.g. {'text': 'Hello', 'color': 'gold', 'bold': true}, or a list of components. Plain text is wrapped as {'text': ...}.
targetYesPlayer name or selector such as @a or @a[distance=..10] (no spaces).

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 the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the bar is lower. The description adds genuinely useful context by naming 'vanilla /tellraw', which tells the agent this works without server plugins and that the payload is Minecraft's raw JSON text format. It does not mention delivery scope (who sees it), failure modes, or rate limits.

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?

One front-loaded sentence, no filler, with the mechanism and the formatting traits packed into the parenthetical. Every clause earns its place.

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?

An output schema exists, so return values need not be explained, and both parameters are fully described in-schema. What remains thin is routing guidance against send_message/broadcast_message, which is the main thing an agent could still get wrong.

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% and both parameters are well documented in-schema, including the anyOf shape for text and the selector pattern for target. The description adds nothing parameter-level beyond the schema, so 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?

States a specific verb (send) and resource (chat message), plus the mechanism (vanilla /tellraw) and the distinguishing trait (formatted: coloured, clickable, hoverable). This implicitly separates it from the plain send_message/broadcast_message siblings, but never names them, so the differentiation is inferential rather than explicit.

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 word 'formatted' plus the '/tellraw' mechanism implies you reach for this when you need rich text and plain text elsewhere, but there is no explicit when-to-use statement, no exclusion, and no named alternative. An agent must infer the routing from sibling names alone.

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