Skip to main content
Glama

Put a scene back to normal

release_scene
DestructiveIdempotent

End one scene: its screens go back to their own content.

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": {
      "scene_id": "<scene_id>"
    },
    "name": "release_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_idYesId of the scene, as listed with the team's scenes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / scene_id / description
      Added value: +"Id of the scene, as listed with the team's scenes."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description adds real value by explaining what the destruction means concretely: screens revert to their own content. However it never says whether the scene object itself is deleted or merely deactivated, whether it can be re-activated, or whether the revert is instant or has side effects on other screens.

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?

A single short sentence that front-loads the action and immediately explains the effect. No filler, no redundancy.

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?

For a one-parameter, non-read-only operation with no output schema, the description covers the visible effect but leaves the state model ambiguous: whether the scene survives in a releasable/activatable form matters given the sibling activate_scene. Enough to call it, not enough to reason confidently about the result.

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%, so scene_id is fully documented in the schema including its UUID pattern. The description adds no additional meaning about which scene id is expected or how to obtain it, so the baseline 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 concrete action (ending a scene) and its observable effect ('its screens go back to their own content'), and the word 'one' implicitly scopes it against the release_all sibling. It stops short of naming activate_scene or release_all as counterparts, so the boundary is inferable rather than stated.

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?

Usage is only implied: the agent can guess this is for tearing down a single active scene, but there is no explicit when-to-use guidance, no prerequisites (does the scene need to be active first?), and no mention of release_all or release_screen as alternatives. Adequate but leaves routing to inference.

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