Skip to main content
Glama

Add a scene

add_scene

Add one scene at the end of a project, with its script: what the recorder's teleprompter shows (the words to say, not stage directions). Free. Returns the scene and how many scenes there are.

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": {
      "project_id": "<project_id>",
      "title": "<title>"
    },
    "name": "add_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
scriptNoThe scene's script: the words the teleprompter shows while the person records: what to say, not stage directions
project_idYesFrom create_project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (non-read-only, non-destructive, non-idempotent), and the description adds genuinely new context: the operation is 'Free' (cost implication) and it returns the scene plus the total scene count, useful since no output schema exists. It also discloses the append-only placement behavior, which annotations do not express.

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 short sentences, front-loaded with the core action and placement, followed by script semantics and return behavior. The parenthetical about the teleprompter partially duplicates the schema but is defensible as disambiguation.

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 simple 3-parameter mutation with no output schema, the description covers what is created, where, what the script means, cost, and return shape. Only the 'title' parameter's semantics and its relationship to the scene identity are left unaddressed.

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 67%, and the description's script explanation largely restates the schema's own 'script' description while adding the 'not stage directions' emphasis. It says nothing about 'title' (undocumented in schema) or about 'project_id' beyond the schema's 'From create_project' note.

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 names a specific verb and resource ('Add one scene') plus its placement scope ('at the end of a project'), so the agent knows exactly what gets created and where. It does not differentiate from near siblings such as make_screen_scene or add_screens, so it stops 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?

Usage is implied by 'at the end of a project' and the script clarification, but there is no explicit when-to-use/when-not guidance and no mention of when to prefer make_screen_scene, update_scene, or add_screens. 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