Skip to main content
Glama

storyline.set_candidates

Replace the current batch of suggested next scenes with distinct options you propose, so the user can pick one. Each option should follow from the premise and every scene already in the path.

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>",
      "candidates": "<candidates>"
    },
    "name": "storyline.set_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes
candidatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key mutation trait: the current batch is *replaced*, so prior suggestions are destroyed. It does not say whether a premise or non-empty path is required, whether there is a maximum number of candidates, or whether anything is persisted or versioned.

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?

Two tight sentences with the replacement semantics front-loaded and the quality constraint second; nothing is redundant. Slightly more length would be justified to cover the missing parameter and call-path details.

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 mutation tool with no annotations and no output schema, the definition covers the destructive-replacement behavior and content expectations but omits prerequisites, candidate count limits, and its relationship to storyline.suggest/storyline.pick. An agent could call it, but would have to guess at scale and sequencing.

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

Parameters2/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, yet it explains almost no parameter semantics — projectId is never mentioned, and of the seven candidate fields (title, plannedDurationMs required; summary, soundPrompt, videoPrompt, voicePrompt, narrativePurpose optional) only the abstract notion of 'distinct options' is addressed. It adds a content constraint ('follow from the premise and every scene already in the path') but no guidance on count, unicity, or how to populate the prompt fields.

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 verb and resource ('Replace the current batch of suggested next scenes with distinct options you propose') and makes the user-facing outcome explicit ('so the user can pick one'). It is clear what the tool does, but it does not distinguish itself from the nearby siblings storyline.suggest and storyline.pick, leaving the agent to infer the division of labor.

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 phrase 'so the user can pick one' hints that selection happens downstream (presumably via storyline.pick), but there is no explicit when-to-use versus storyline.suggest, no precondition such as requiring a premise or existing path, and no statement of when not to call it.

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.