Skip to main content
Glama
newsbubbles

ismail: agent DAW (MCP server)

Stage Set Load

stage_set_load

Load or unload a scene's load set to hide or restore its meshes, shadows, and people; unloaded sets show ghost boxes and persist across reloads via world.json.

Instructions

Unload a load set (loaded=False) or load it again (loaded=True, the default). Unloaded: its meshes are not drawn, cast no shadow, and at the next load are never compiled or uploaded (on an open page, what only the set used is freed on the GPU now); the people in it stop and neither play, follow nor rest; a ghost box around each member and a label with the set's name stand in its place. Loaded: it comes back a piece at a time. Saved in world.json unloaded, so it holds across reloads; an open page changes now (page command load_set) and replies with what it hid or showed ({name, items, persons, meshes, tris, freed}). Emits: set_unloaded / set_loaded {name, items, persons, meshes, tris}.

Input Schema

NameRequiredDescriptionDefault
nameYes
sceneYes
loadedNo
scenesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A3.7/5.0
Behavior5/5

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

With no annotations present the description carries the full burden and does so thoroughly: meshes stop drawing, cast no shadow, GPU resources are freed now vs. recompiled at next load, people halt, ghost boxes and a set-name label stand in, and the state persists in world.json across reloads. It also lists the reply payload and emitted events (set_unloaded/set_loaded).

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 core action is front-loaded in one sentence and the remaining sentences are dense with behavior rather than filler. The parenthetical-heavy phrasing and long clauses make it slower to parse than it needs to be.

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?

Persistence semantics, live-page behavior, events, and the reply shape are all covered, and an output schema exists so return-format detail is only lightly needed. The one real hole is the unexplained `scene`/`scenes` parameters, which an agent cannot resolve from the description.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters. The description explains `loaded` well (both values plus the default true), and the set `name` is implied by the label reference, but `scene` and especially the opaque `scenes` string (default null) receive no explanation anywhere.

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 first sentence names a specific verb and resource — unload or re-load a load set — and encodes the state in the `loaded` flag, so the agent knows exactly what the tool does. It does not explicitly distinguish itself from nearby siblings like stage_sets or stage_set_define, which keeps it short of a 5.

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?

It clearly explains the two usage modes (loaded=False to hide, loaded=True/default to restore) and notes that an already-open page reacts immediately. It gives no guidance on when to pick this tool over stage_sets/stage_set_define, and no prerequisites or exclusions are stated.

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

Deploy Server

Other Tools