Skip to main content
Glama

chat

Send a local-only progress message to the Minecraft player so users can follow agent actions; configured tags, names, and colors are applied automatically.

Instructions

Display a progress message in the player’s local Minecraft chat. The configured tag, name and colors are added automatically. Only the local player sees it.

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": "chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden. It does add useful behavior: a local-only visibility scope and automatic tag/name/color formatting. It omits rate limits, whether output confirms delivery, and whether the message is escaped or rendered as-is.

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?

Three short sentences, front-loaded with the action, then the automatic formatting, then the visibility scope. Nothing is wasted and the most decision-relevant fact (local only) is stated plainly.

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 one-parameter, no-output-schema tool this covers the essentials: what it does, who sees it, and what formatting is handled for the caller. Only minor gaps remain (return value confirmation, escaping behavior), which is acceptable at this complexity.

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 0% with one parameter, and the description does note that the message is displayed and that prefix/tag and colors are added automatically – telling the agent not to embed formatting. However, it does not state that the single field is the message body, nor mention the 2000-character limit or plain-text handling.

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?

Specific verb and resource: "Display a progress message in the player's local Minecraft chat." It clearly states the effect and audience (local player only), so an agent can tell this apart from a general execution tool, though it does not name any 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?

The phrase "progress message" implies the intended context (user-facing status updates during long operations), but there is no explicit when-to-use, when-not-to-use, or comparison to alternatives like execute. Usage must be inferred from the wording.

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

Deploy Server

Other Tools