Skip to main content
Glama

project_import

DestructiveIdempotent

Imports a directory or exported ZIP into a task's project path, preserving relative paths, binary files, and helpers while reusing identical files and reporting conflicts instead of overwriting.

Instructions

Import a directory or exported ZIP into the task's project_path, retaining relative paths, binary files and helpers.

Existing identical files are reused; differing files cause a conflict, never overwrite. ZIP hashes and original records are checked. Returns operation_id immediately. Release any task_claim before waiting on operation_get; read task_get for the new revision after completion.

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": {
      "task_id": "<task_id>",
      "revision": "<revision>",
      "source": "<source>",
      "op_id": "<op_id>"
    },
    "name": "project_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
sourceYes
task_idYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

The description adds real behavior beyond the annotations: identical files are reused, differing files raise a conflict and are never overwritten, and ZIP hashes plus original records are checked. Combined with destructiveHint=true, the agent learns the write is conflict-guarded and idempotent, which reconciles the flagged traits. It still omits auth/permission requirements for a destructive mutation.

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?

Five tight sentences, front-loaded with purpose followed by conflict semantics and workflow. The only friction is the 'returns operation_id' sentence, which is terse enough to be ambiguous against the required op_id input rather than wasteful.

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?

An output schema exists, so return values needn't be explained, and the description still covers the async handoff and safety posture of a destructive write. What remains missing is authorization expectations and any size or scope constraints on the imported directory, which matter for a mutation over a project tree.

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% across five parameters, so the description must carry the load and largely does not. It clarifies that source is a directory or exported ZIP and refers obliquely to revision via task_get, but token is never explained and the required op_id is muddled by the statement that the call 'returns operation_id immediately', leaving it unclear whether op_id is supplied or produced.

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?

The description gives a specific verb and resource: importing a directory or exported ZIP into the task's project_path, with fidelity details (relative paths, binary files, helpers). It is clearly distinct from siblings like project_export and resource_catalog_import, though it never explicitly names the alternative it is not.

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?

It supplies concrete workflow context: release any task_claim before waiting, call operation_get for status, and read task_get for the new revision after completion. That tells the agent how to sequence the call, but it never states when to pick import over project_snapshot or resource_catalog_import, so the alternative-selection guidance is incomplete.

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