Skip to main content
Glama

story_refresh_scene

Idempotent

Bring one scene up to date with the latest script after story_update_script. Free. Refused once the scene has a video.

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": "story_refresh_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover mutation/idempotency (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description adds two things they do not: the operation is free, and it is rejected once the scene has a video. It still does not say what state the scene ends in (e.g. whether a re-render is required), which is the main remaining behavioral gap.

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?

Three short sentences, each load-bearing: purpose, cost, failure precondition. Nothing is repeated and the purpose leads.

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 one-parameter mutation with no output schema, the description covers purpose, cost and the refusal condition. It does not describe the result of the refresh or the follow-up workflow (e.g. re-rendering or re-generating the scene's video), leaving the agent to infer what to do next.

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% for scene_id, so the description carries the burden but adds no meaning beyond the name. Since scene_id is a self-explanatory UUID, the gap is small, but the description offers no hint about where to obtain a valid scene id.

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?

States a specific verb and resource with explicit scope: 'Bring one scene up to date with the latest script.' It also names the sibling it depends on (story_update_script), letting an agent separate it from script-level and project-level tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear sequencing rule ('after story_update_script') and an explicit exclusion ('Refused once the scene has a video'), which tells the agent both when this is valid and when it will fail. It does not name an alternative tool for the cases it excludes, so it falls just short of the top band.

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