Skip to main content
Glama

send-chat

Send chat messages in Minecraft to communicate with players or execute commands through the MCP server.

Instructions

Send a chat message in-game

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage to send in chat

Implementation Reference

  • The handler function that executes the tool logic: retrieves the bot and calls bot.chat(message), then returns a response.
    async ({ message }) => {
      const bot = getBot();
      bot.chat(message);
      return factory.createResponse(`Sent message: "${message}"`);
    }
  • Input schema definition using Zod for the 'message' parameter.
    {
      message: z.string().describe("Message to send in chat")
    },
  • Registration of the 'send-chat' tool using factory.registerTool, including name, description, schema, and inline handler.
    factory.registerTool(
      "send-chat",
      "Send a chat message in-game",
      {
        message: z.string().describe("Message to send in chat")
      },
      async ({ message }) => {
        const bot = getBot();
        bot.chat(message);
        return factory.createResponse(`Sent message: "${message}"`);
      }
    );
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action without behavioral details. It doesn't disclose permissions needed, rate limits, whether the message is broadcast or targeted, or any side effects, which is insufficient for a mutation tool.

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?

The description is a single, efficient sentence with no wasted words, front-loading the core action. It's appropriately sized for a simple tool, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context (e.g., effects, permissions) and doesn't explain return values, leaving significant gaps for agent understanding.

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 the schema fully documents the single parameter 'message'. The description doesn't add any semantic context beyond what the schema provides, such as message length limits or formatting rules, meeting the baseline for high coverage.

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 clearly states the action ('send') and resource ('a chat message in-game'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'read-chat', but it's specific enough to convey the core function without being tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., being in a game session), exclusions, or how it relates to siblings like 'read-chat', leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yuniko-software/minecraft-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server