Skip to main content
Glama

Broadcast message

broadcast_message

Sends a chat message to all players on a Minecraft server, displayed as '[Server] ', so agents can announce updates or instructions globally.

Instructions

Send a chat message to every player; it appears as '[Server] '.

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

Input Schema

NameRequiredDescriptionDefault
messageYesMessage text.

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 this is a non-read-only, non-destructive, non-idempotent, closed-world call, so the safety profile is covered structurally. The description adds genuinely useful behavioral context by stating how the message is rendered to recipients ('[Server] <message>'). It says nothing about permissions, rate limits, or whether repeated identical broadcasts are deduplicated, which is the notable gap for a fan-out write.

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?

A single compact sentence with the action first and the rendering detail second. Nothing is wasted and nothing is buried.

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 tool with a documented schema and an output schema, the definition covers what the agent needs to call it correctly. The only shortfall is the absence of any note on delivery scope edge cases (e.g., whether the sending player is included) or permission requirements.

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 100% and there is only one parameter, so the schema already carries the burden of length bounds and type. The description's display-format detail clarifies how the message text is presented, which is mild added meaning, but it does not explain any transformation, escaping, or formatting rules applied to the input.

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 uses a concrete verb+resource pair ('Send a chat message') plus an explicit scope ('to every player'), which separates it from a targeted send. It stops short of naming a sibling like send_message, so the distinction is inferred from 'every player' rather than stated.

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?

Broadcast scope is implied strongly by 'every player', giving the agent enough to choose this over a single-recipient tool. However, there is no explicit when-to-use / when-not-to-use statement and no mention of alternatives such as send_rich_message for formatted output.

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