Skip to main content
Glama

studio_import_project

Imports a versioned production manifest from local disk, including asset hashes, character bible, and shots, so a project can be restored and tracked with verified file integrity.

Instructions

Import a versioned production manifest with asset hashes, character bible and shots from local disk.

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": {
      "manifestPath": "<manifestPath>"
    },
    "name": "studio_import_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a mutating import but does not say whether it overwrites or merges an existing project, how asset-hash mismatches or invalid manifests are handled, whether the operation is idempotent, or what permissions are needed.

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?

A single front-loaded sentence with no filler; the payload contents are enumerated compactly. Nothing is wasted, though the enumeration is dense enough to require careful reading.

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?

For a mutation-style import with no annotations and no output schema, the description should explain side effects, failure behavior, and the result. None of that is present, so an agent knows what it imports but not what happens when it does.

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 coverage is 0%, but there is only one trivially simple parameter (manifestPath, a non-empty string). The phrase 'from local disk' weakly signals that the argument is a filesystem path, yet the description gives no format, path convention, or size/validity constraints beyond the schema's minLength.

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 (Import) and a well-scoped resource (a versioned production manifest with asset hashes, character bible and shots) plus the source (local disk). It is distinguishable from siblings like studio_ingest_result or studio_bind_project, though it never explicitly contrasts itself with them.

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?

There is no when-to-use or when-not-to-use guidance and no prerequisites or ordering hints (e.g. whether preflight or plan should run first). The only implicit cue is 'from local disk', which tells the agent the source but not the situation that selects this tool over studio_bind_project or studio_ingest_result.

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