Skip to main content
Glama
zeeweebee

Minecraft MCP Server

by zeeweebee

send-chat

Send chat messages in Minecraft through an MCP server, enabling AI-controlled characters to communicate in-game.

Instructions

Send a chat message in-game

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage to send in chat

Implementation Reference

  • The handler function for the 'send-chat' tool. It sends the provided message using bot.chat(message) and returns a success response or error.
    async ({ message }): Promise<McpResponse> => {
      try {
        bot.chat(message);
        return createResponse(`Sent message: "${message}"`);
      } catch (error) {
        return createErrorResponse(error as Error);
      }
    }
  • Input schema for the 'send-chat' tool, defining a required 'message' parameter as a string.
    {
      message: z.string().describe("Message to send in chat")
    },
  • src/bot.ts:532-548 (registration)
    Registers the 'send-chat' tool with the MCP server, including name, description, schema, and handler function.
    function registerChatTools(server: McpServer, bot: any) {
      server.tool(
        "send-chat",
        "Send a chat message in-game",
        {
          message: z.string().describe("Message to send in chat")
        },
        async ({ message }): Promise<McpResponse> => {
          try {
            bot.chat(message);
            return createResponse(`Sent message: "${message}"`);
          } catch (error) {
            return createErrorResponse(error as Error);
          }
        }
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'in-game' context but fails to address critical aspects like whether this requires specific permissions, if there are rate limits, what happens if the message fails to send, or any side effects. The description is minimal and lacks behavioral context.

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 that directly states the tool's function without any wasted words. It's appropriately sized for a simple tool and front-loaded with the core action.

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 (sending a message implies a write operation) with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after sending, potential errors, or the game context needed. The description should provide more complete guidance given the tool's complexity and lack of structured data.

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?

The input schema has 100% description coverage, with the 'message' parameter clearly documented. The description doesn't add any semantic details beyond what the schema provides, such as message length limits or content restrictions. Baseline 3 is appropriate when the schema does the heavy lifting.

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 target ('a chat message in-game'), making the purpose immediately understandable. It doesn't differentiate from siblings, but none of the listed sibling tools appear to be chat-related alternatives, so this is adequate.

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?

The description provides no guidance on when to use this tool versus alternatives or any contextual prerequisites. It simply states what the tool does without indicating appropriate scenarios or limitations.

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/zeeweebee/mcp-server'

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