Skip to main content
Glama

story_get_project

Read-onlyIdempotent

Start here for an existing project. Returns progress — is the script still being analysed, how many assets lack a picture, which scenes have storyboards and videos — plus next_step (wait_for_script_breakdown, fix_script, generate_asset_images, generate_storyboards, generate_scene_videos, choose_takes, done) and the episode ids. Free.

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>"
    },
    "name": "story_get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral value beyond them: the full next_step state machine (wait_for_script_breakdown through done), which tells the agent this tool drives workflow routing, and "Free" which discloses there is no generation cost. It does not describe rate limits or auth, but those are minor here.

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?

Front-loaded with the entry-point cue, then a dense enumeration of returned fields and an inline next_step enum. No filler sentences; every clause carries information.

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?

With no output schema, the description compensates well by listing the returned progress signals, the next_step values, and episode ids. It leaves the exact shape of the response loosely defined and says nothing about the project_id format, but for a single-parameter status tool this is close to complete.

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 the single project_id parameter, so the description technically carries the burden. However project_id is trivially named and the schema supplies format=uuid and required status; "for an existing project" only loosely implies the id must reference a real project. Marginal value over the schema, so 3.

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 ("Returns progress" for an "existing project") and enumerates exactly what comes back: script analysis status, asset/picture gaps, scene storyboard and video state, plus next_step and episode ids. This is far more concrete than a generic getter and distinguishes it from story_get_job and story_get_episode, though it never explicitly names those siblings.

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?

"Start here for an existing project" is an explicit entry-point instruction that routes the agent to this tool first before the finer-grained story tools. It stops short of naming alternatives or when-not-to-use conditions, so it is clear context rather than full routing guidance.

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