Skip to main content
Glama

Start a scene

activate_scene
Destructive

Put a scene live: every screen and sub-screen in the scene switches at once, in place of what it shows. Running it again puts changes to the scene live. A screen only shows the scene once it is online and has a player paired; each result includes online and paired when the connection may read screens.

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": "activate_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.7/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and openWorldHint=true. The description adds real value beyond that by explaining what is actually overridden: every screen and sub-screen switches in place of what it currently shows. It also states that a screen displays the scene only once it is online and paired, and that results report online and paired status. The final clause, 'when the connection may read screens,' is vague about when those fields are actually returned.

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?

Three sentences, front-loaded with the core action and its effect, with no filler. The last sentence is dense and somewhat ambiguous, which slightly hurts clarity, but overall it is efficient.

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 destructive, single-parameter mutation with no output schema, the definition covers the action, its scope of impact on screens, re-run semantics, and the conditional status fields returned. More explicit guidance on prerequisites and on the sibling release_scene tool would make it complete, but nothing essential is missing.

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?

There is a single parameter with 100% schema coverage, including a UUID pattern and a description of where the scene ID comes from. The definition adds nothing about the parameter beyond what the schema already provides, so the baseline score 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?

The description gives a concrete verb and resource: it puts a scene live, switching every screen and sub-screen in the scene at once. This is much clearer than the title alone. However, it does not name or distinguish the tool from its sibling release_scene, so an agent must infer the difference between activation and release.

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?

The description implies a two-phase workflow: run once to go live, and run again to publish subsequent scene changes. It does not state any when-not conditions, prerequisites such as scene readiness, or which sibling to use for releasing content instead. The usage guidance is therefore implied rather than explicit.

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