Skip to main content
Glama

storyline.rewind

Rewind the storyline: keep only the first keep accepted scenes (0 clears the path) and discard the rest and the current candidates, so a different choice can be made at that point.

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>",
      "keep": "<keep>"
    },
    "name": "storyline.rewind"
  }
}

Input Schema

NameRequiredDescriptionDefault
keepYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the destructive core: accepted scenes beyond `keep` and the current candidates are discarded, and `keep=0` clears the path entirely. It stops short of stating whether the rewind is reversible or how it interacts with project.undo, which matters for a destructive mutation.

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 sentence, front-loaded with the verb and resource, then the precise effect, then the motivation. No redundant or filler wording.

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 two-parameter destructive mutation with no annotations and no output schema, the description covers what is destroyed and the edge case of `keep=0`. The remaining gap is reversibility/undo behavior, which an agent would want before invoking a discard operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does for the non-obvious parameter: `keep` is defined as a count of accepted scenes with the special case 0 clearing the path. `projectId` is left unexplained, but its meaning is self-evident from the name.

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?

The description names a specific verb (rewind) and resource (storyline) and defines the exact effect: keep the first `keep` accepted scenes, discard the rest plus current candidates. This is clearly distinguishable from siblings like storyline.pick or storyline.apply, which advance rather than truncate the path.

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 trailing clause 'so a different choice can be made at that point' implies the use case (backtracking to re-pick), but there is no explicit when-not guidance and no named alternative such as project.undo for reversing the operation. Usage is inferable rather than stated.

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.