Skip to main content
Glama

import_project

Imports a .drp project file or restores a .dra archive into the current project-manager folder; set restore_archive to true to restore an archive.

Instructions

Import a .drp project file (or restore a .dra archive with restore_archive=true) into the current project-manager folder.

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": {
      "path": "<path>"
    },
    "name": "import_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
pathYes
restore_archiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description usefully pins the destination to the current project-manager folder, but says nothing about overwrite/conflict behavior or whether the imported project is left open afterward.

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?

A single front-loaded sentence that names the resource, the alternate mode, and the destination with no wasted wording.

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?

With no output schema and zero parameter coverage, the description should explain the undocumented 'name' parameter and conflict/overwrite semantics for a write operation. It covers the core action adequately but leaves these gaps.

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%, so the description must compensate. It explains restore_archive and constrains path to .drp/.dra files, but the 'name' parameter is never mentioned, leaving one of three parameters undocumented in both schema and description.

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 resource (.drp project file / .dra archive) plus the destination (current project-manager folder). This distinguishes it from media/timeline importers, though it does not explicitly name a sibling such as open_project for contrast.

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?

The description implies when to use the restore path (restore_archive=true for .dra archives), but gives no guidance on when to import vs. open an existing project, or what happens if a project with the same name already exists. Usage is inferable rather than stated.

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

Deploy Server

Other Tools