Skip to main content
Glama

Lightning, explosions, sounds, particles

world_effect
Destructive

Triggers lightning, explosions, sounds, or particles at a chosen Minecraft location to create live world events, with options for harmless flashes, terrain-breaking blasts, and nearby audio.

Instructions

Make something happen at a location. lightning strikes (effectOnly makes it harmless). explosion blows up with power (TNT is 4); breakBlocks destroys terrain and fire sets things alight. sound plays a sound such as minecraft:entity.ender_dragon.growl for everyone nearby. particles shows particles such as minecraft:heart or minecraft:flame; ones that need extra data (dust, block) aren't supported.

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": {
      "kind": "<kind>",
      "location": "<location>"
    },
    "name": "world_effect"
  }
}

Input Schema

NameRequiredDescriptionDefault
fireNoexplosion
kindYesPicks the fields that apply
countNoparticles: 10 by default
pitchNosound
powerNoexplosion: 4 by default
soundNosound: the sound key
speedNoparticles
worldNoWorld name, such as `world`, `world_nether`, `world_the_end`, or a key like `minecraft:the_nether`world
offsetNoparticles: spread
volumeNosound
categoryNosound: `master` by default
locationYesA spot in a world; y is height (the overworld runs from -64 to 319)
particleNoparticles: the particle key
effectOnlyNolightning: only the flash and the sound
breakBlocksNoexplosion

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.2.1
    • addedInput schema / properties / kind / description
      Added value: +"Picks the fields that apply"
  2. First observedv4.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and non-idempotence, but the description adds useful behavioral context: `effectOnly` makes lightning harmless, `breakBlocks` destroys terrain, `fire` sets things alight, sound is heard by nearby players, and particles requiring extra data are unsupported. It stops short of mentioning permissions, exact world mutation scope, or return behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph that front-loads the general purpose and then covers each mode compactly with backticked field names. It is appropriately sized for a 15-parameter tool, though the opening sentence is vague and the paragraph could be slightly more scannable.

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 complex 15-parameter tool with a nested location object and no output schema, the description covers all four effect kinds and the most important side effects and limitations. Remaining parameter details are supplied by the 100%-covered schema, so the agent has enough to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds real semantic value beyond the schema: TNT-equivalent power of 4, harmless lightning via `effectOnly`, example sound and particle keys, and the limitation that complex particles such as dust or block are unsupported.

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 that this tool creates a world effect at a location and enumerates the four supported kinds: lightning, explosion, sound, and particles. It distinguishes the effect modes from one another, but does not distinguish the tool from siblings such as set_blocks, spawn_entity, send_message, or run_command.

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 explains what each `kind` does but gives no explicit guidance on when to choose world_effect over alternatives, nor any prerequisites or when-not-to-use conditions. The agent must infer usage from the mode descriptions alone.

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