Skip to main content
Glama

project_import

Imports a .drp project file or restores a .dra archive, optionally opening it; set a new name to restore a snapshot alongside the original.

Instructions

Import a .drp project file (or restore a .dra archive with archive=true), optionally opening it. Use a new name to restore a snapshot next to the original.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
openNo
pathYes
archiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a mutating import. It discloses format handling, the default-open behavior, and that a new `name` restores a snapshot next to the original, but says nothing about overwrite behavior, what happens to an existing project of the same name, permissions, or failure modes — significant omissions for an import/restore operation.

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?

Two sentences, front-loaded with the primary action and format, with no filler. The second sentence leans on unstated context about snapshots, which slightly reduces standalone clarity but not the economy of the text.

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 four-parameter mutation with no annotations and no output schema, the description covers formats and modes but omits side effects, conflicting-name behavior, and the result of the operation. It is adequate to call the tool, but not sufficient to predict its consequences.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does for three of four parameters: `archive` toggles .dra handling, `open` controls whether the project is opened, and `name` restores a snapshot under a new name. Only `path` is left implicit, which is a minor residual gap rather than a systemic one.

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 ('Import a .drp project file') and immediately covers the archive variant ('restore a .dra archive with archive=true'), which an agent could not infer from the name alone. It stops short of distinguishing itself from close siblings such as project_open or project_create, so it is clear but not fully differentiated.

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?

Gives conditional guidance for two of the four parameters (archive=true for .dra, a new `name` to restore a snapshot alongside the original), which implies when each mode applies. It never states when to choose this over project_open or project_create, nor any prerequisites or exclusions, so usage is implied rather than explicit.

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