Skip to main content
Glama

Spawn particles

spawn_particles

Show particles at a position in the main world, visible to nearby players. Specify particle type, coordinates, count, spread, and speed.

Instructions

Show particles at a position in the main world (visible to nearby players).

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": {
      "particle": "<particle>",
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "spawn_particles"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesExact X; block centres are at .5 (e.g. 100.5).
yYesExact Y of the feet.
zYesExact Z; block centres are at .5 (e.g. -20.5).
dxNoRandom spread along this axis, in blocks.
dyNoRandom spread along this axis, in blocks.
dzNoRandom spread along this axis, in blocks.
countNoNumber of particles.
speedNoParticle speed.
particleYesParticle such as 'flame', 'heart', 'happy_villager', 'end_rod', 'cloud' or 'soul_fire_flame'. Particles that need extra data (dust, block, item) are not supported.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=false and destructiveHint=false, so the safety profile is supplied. The description earns some credit for adding 'visible to nearby players', which signals the effect is client-side and observer-dependent rather than a stored world change. It still omits that the effect is transient/fire-and-forget and that only the main world is addressable (no nether/end), which matters given idempotentHint=false.

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?

A single front-loaded sentence with no redundancy; every clause ('main world', 'visible to nearby players') carries information. It is arguably too thin for a 9-parameter mutation-ish tool, but nothing in it is wasted.

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

Completeness3/5

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

An output schema exists and the input schema is fully documented, so return values and argument formats need not be repeated. However, for a tool with nine parameters and idempotentHint=false, the description leaves the agent uninformed about the transient, non-persistent nature of the effect and its world restriction beyond 'main world'.

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% across all 9 parameters, including block-centre coordinates, spread axes, count bounds, speed, and unsupported particle types. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Show particles at a position') and scopes it to 'the main world', which tells an agent the effect is world-bound rather than global. It does not differentiate from any sibling (e.g. spawn_loot or apply_effect), so an agent must infer the boundary between visual effects and other spawn/effect tools.

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?

There is no when-to-use guidance, no exclusions, and no named alternative. The one genuinely useful exclusion (unsupported particle types that need extra data, such as dust/block/item) lives in the schema's particle property rather than the description, so the description itself gives no routing guidance.

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