Skip to main content
Glama

scene-delete

Destructive

Delete a scene with everything on it, or only one of its levels when levelId is given (Foundry 14+). Cannot be undone. Requires bridge module 8.19.0+.

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": {
      "sceneId": "<sceneId>"
    },
    "name": "scene-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelIdNoLevel ID (from scene-get levels) — delete just this level
sceneIdYesScene ID (from scene-list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely useful context beyond them: irreversibility ('Cannot be undone'), the cascade scope ('with everything on it'), and hard version requirements for both Foundry and the bridge module. It does not cover permission/auth needs, which keeps it at 4.

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?

Three short sentences, front-loaded with the primary action and scope, then the conditional mode, then the irreversible/version caveats. No filler words; every clause carries information.

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

Completeness5/5

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

For a two-parameter destructive tool with full annotation coverage and no output schema, the description supplies everything an agent needs to call it correctly: scope of deletion, the levelId switch, irreversibility, and version prerequisites.

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 the levelId description already says 'delete just this level', so the description's parameter guidance largely restates structured information. It does add the cross-cutting point that omitting levelId deletes the whole scene including contents, but that is marginal value over the schema.

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?

States a specific verb and resource (delete a scene) and immediately scopes two distinct modes: full scene with all contents, or a single level when levelId is supplied. An agent can tell exactly what this tool does and how its two behaviors differ.

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

Usage Guidelines4/5

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

Gives a clear inline rule for choosing between the two modes (levelId present → level-only deletion) and states prerequisites (Foundry 14+, bridge module 8.19.0+). It stops short of naming alternatives or explicit when-not-to-use conditions, so it falls just shy of a 5.

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