Skip to main content
Glama

storyline.set_premise

Set the Scenario Maker premise (initial scene or short scenario), optionally with up to 3 reference images (base64) that define the look and setting. Resets the accepted path and candidates. Needs a premise or at least one image.

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": {
      "projectId": "<projectId>"
    },
    "name": "storyline.set_premise"
  }
}

Input Schema

NameRequiredDescriptionDefault
imagesNo
premiseNo
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one important destructive side effect: setting a premise "Resets the accepted path and candidates." That is real behavioral context. It still omits whether the reset is recoverable (storyline.rewind exists as a sibling), permission/auth requirements, and what happens to already-created scenes or shots.

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 action and resource, followed by the optional input and then the side effect. No filler or repetition; slightly dense phrasing ("premise (initial scene or short scenario)") but every clause carries information.

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 mutating, state-resetting tool with no annotations and no output schema, the description covers the input contract and one side effect but leaves the agent guessing about recoverability, downstream impact on existing candidates/scenes, and what the call returns. Adequate minimum, but not complete for a tool that clears prior work.

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 0%, so the description must compensate. It adds useful meaning for two of three params: images are base64, capped at 3, and define "look and setting"; premise is the initial scene. It also encodes the at-least-one-of constraint the schema does not. But projectId is never explained, and the base64/data format is only loosely implied.

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 specific verb and resource ("Set the Scenario Maker premise") plus what the premise is ("initial scene or short scenario") and the optional image input. It hints at the sibling relationship by noting it "Resets the accepted path and candidates," but it never names set_candidates or pick explicitly, so differentiation is implied 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?

The precondition "Needs a premise or at least one image" is genuinely useful usage guidance that the schema cannot express (only projectId is required there). However, there is no guidance on when to call this versus storyline.set_candidates, storyline.suggest, or storyline.update_scene, nor on when it should be re-run.

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.