Skip to main content
Glama

read-chat

Retrieve recent chat messages from Minecraft players to monitor in-game conversations and interactions.

Instructions

Get recent chat messages from players

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of recent messages to retrieve (default: 10, max: 100)

Implementation Reference

  • The asynchronous handler function for the 'read-chat' tool. It retrieves a specified number of recent chat messages from the messageStore (clamped to max), formats them with timestamps, usernames, and content, and returns a formatted response string using factory.createResponse.
    async ({ count = 10 }) => {
      const maxCount = Math.min(count, messageStore.getMaxMessages());
      const messages = messageStore.getRecentMessages(maxCount);
    
      if (messages.length === 0) {
        return factory.createResponse("No chat messages found");
      }
    
      let output = `Found ${messages.length} chat message(s):\n\n`;
      messages.forEach((msg, index) => {
        const timestamp = new Date(msg.timestamp).toISOString();
        output += `${index + 1}. ${timestamp} - ${msg.username}: ${msg.content}\n`;
      });
    
      return factory.createResponse(output);
    }
  • Zod schema definition for the optional 'count' input parameter (number, default 10, max 100).
    {
      count: z.number().optional().describe("Number of recent messages to retrieve (default: 10, max: 100)")
    },
  • Registers the 'read-chat' tool via factory.registerTool, including name, description, schema, and inline handler.
    factory.registerTool(
      "read-chat",
      "Get recent chat messages from players",
      {
        count: z.number().optional().describe("Number of recent messages to retrieve (default: 10, max: 100)")
      },
      async ({ count = 10 }) => {
        const maxCount = Math.min(count, messageStore.getMaxMessages());
        const messages = messageStore.getRecentMessages(maxCount);
    
        if (messages.length === 0) {
          return factory.createResponse("No chat messages found");
        }
    
        let output = `Found ${messages.length} chat message(s):\n\n`;
        messages.forEach((msg, index) => {
          const timestamp = new Date(msg.timestamp).toISOString();
          output += `${index + 1}. ${timestamp} - ${msg.username}: ${msg.content}\n`;
        });
    
        return factory.createResponse(output);
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It lacks information on permissions, rate limits, data freshness, or response format, which are critical for a read operation in a gaming 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 with zero wasted words. It's front-loaded with the core action and resource, making it highly concise and well-structured for quick understanding.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'recent' means, how messages are ordered, or what the return format is, leaving significant gaps for a tool that retrieves 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?

Schema description coverage is 100%, so the schema fully documents the 'count' parameter. The description adds no parameter-specific semantics beyond implying retrieval of 'recent' messages, which is minimal value over the schema's details.

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 verb ('Get') and resource ('recent chat messages from players'), making the purpose immediately understandable. However, it doesn't differentiate from potential sibling tools like 'send-chat' beyond the obvious directionality, missing explicit comparison.

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. While 'send-chat' is a sibling, the description doesn't mention it or any other tools, leaving the agent to infer usage context without explicit direction.

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