Skip to main content
Glama

Show a design in 3D

show
Read-onlyIdempotent

Show a design to the user in an interactive 3D viewer in the chat: they can press its button or flip its lever, watch it run tick by tick, move around, and click any part to read what it does. Give either design, or example (an id from list_examples). Call it once per answer, at the end, after the last simulate passes: every call adds another viewer to the chat. Do not use it to test a design: use simulate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "show"
  }
}

Input Schema

NameRequiredDescriptionDefault
designNoA machine: a list of blocks plus what it is for. See the server instructions for block types and rules.
exampleNoId of a built-in example to show instead of a design

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / design / properties / test / properties / inputs / description
      Previous value: -"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), strike (lightning strikes a lightning rod), turn_page (lectern), open and close (chest or trapped chest; for stand, leave, open and close an optional player 1-4, default 1), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"New value: +"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), strike (lightning strikes a lightning rod), turn_page (lectern), open and close (chest or trapped chest; for stand, leave, open and close an optional player 1-4, default 1), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a plain minecart on a rail; a hopper minecart goes in the design: \"minecart\": \"hopper\" on the rail)"
  2. Changed1 schema field changed
    • changedInput schema / properties / design / properties / test / properties / inputs / description
      Previous value: -"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), strike (lightning strikes a lightning rod), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"New value: +"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), strike (lightning strikes a lightning rod), turn_page (lectern), open and close (chest or trapped chest; for stand, leave, open and close an optional player 1-4, default 1), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"
  3. Changed1 schema field changed
    • changedInput schema / properties / design / properties / test / properties / inputs / description
      Previous value: -"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"New value: +"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), strike (lightning strikes a lightning rod), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"
  4. Changed1 schema field changed
    • changedInput schema / properties / design / properties / test / properties / inputs / description
      Previous value: -"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame or cake; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"New value: +"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"
  5. Changed1 schema field changed
    • changedInput schema / properties / design / properties / test / properties / inputs / description
      Previous value: -"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor or fence gate; optional look), stand (step onto a pressure plate or string), leave (step off), throw (a snowball at a target), turn_page (lectern), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"New value: +"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame or cake; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"
  6. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnly/idempotent/non-destructive, and the description adds the crucial non-obvious behavior that each call appends another viewer to the chat, which is why it must be called once and last. It does not cover what happens if neither design nor example is supplied, or if both are; that is the only meaningful behavioral gap.

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?

Purpose and interaction model are front-loaded, then input modes, then call cadence, then the sibling exclusion — a sensible order with no filler. The first sentence is long and runs several capabilities together, but every clause adds information an agent needs.

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 deeply nested tool with no output schema and no required parameters, the description covers what the tool produces (an interactive viewer), how many to create, when to create it, and which sibling to use instead. Remaining gaps, such as input validation rules and viewer failure modes, are minor for a read-only presentation tool.

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 coverage is 100%, so the schema carries the baseline, but the description still adds real meaning: the two top-level parameters are alternatives ('either design, or example'), and the example value is sourced from list_examples. The nested schema (blocks, parts, test, view) is left entirely to the schema, which is acceptable given full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Show a design ... in an interactive 3D viewer in the chat') and immediately enumerates the capabilities the user gets: pressing the button, flipping the lever, tick-by-tick playback, orbiting, and clicking parts to read descriptions. An agent can distinguish this from simulate purely from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the exact call policy ('Call it once per answer, at the end, after the last simulate passes') and an explicit exclusion with the replacement named ('Do not use it to test a design: use simulate'). It also tells the agent the two valid input modes — a design or an example id from list_examples.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources