Skip to main content
Glama

studio_sync_plan

List precisely which assets are missing to hydrate one provider-local project for a canonical shot, enabling targeted updates instead of recreating all episodes.

Instructions

List precisely what is missing to hydrate one provider-local project for a canonical shot; never recreate all episodes.

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>",
      "accountId": "<accountId>",
      "shotId": "<shotId>"
    },
    "name": "studio_sync_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
shotIdYes
accountIdYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'List' implies a safe read, but the text never confirms that this is non-mutating, whether it requires registered accounts or bound projects, or what form the plan takes on return; the only real disclosure is the 'never recreate all episodes' caveat.

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?

It is a single front-loaded sentence with no filler, and the scope constraint is stated after the core action. The compactness borders on under-specification given the zero-coverage schema, but there is no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and three undocumented parameters, the description should explain the returned plan's shape and the read-only nature of the call. Instead it leaves the agent guessing about prerequisites and results for a tool whose whole value is the structure of the gap list.

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 all three required parameters are undocumented. The description hints that projectId and shotId identify 'one provider-local project' and 'a canonical shot', but accountId is never mentioned and no parameter semantics, formats, or relationships are clarified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'List' plus the resource 'what is missing to hydrate one provider-local project for a canonical shot' does identify a gap-analysis/planning operation rather than an execution one. However, the phrasing is dense domain jargon and gives no contrast against siblings such as studio_plan or studio_preflight, so an agent cannot easily place it in the catalog.

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

Usage Guidelines2/5

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

The clause 'never recreate all episodes' gestures at a constraint but states no condition for choosing this tool over studio_plan or studio_preflight. There is no when-to-use, when-not-to-use, or prerequisite guidance beyond that fragment.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.