Skip to main content
Glama

project_export

DestructiveIdempotent

Export task project data—files, request, results, history, rules, job accounting, and continuation instructions—into a ZIP archive for handoff to another task via import.

Instructions

Export project files, original request, required results, history, rules, job accounting and continuation instructions to ZIP.

Returns operation_id immediately; release the lease before waiting. operation_get returns the archive's absolute path and hash. Another task can pass that ZIP to project_import. The archive is outside project_path, so do not register its absolute path as a project file. By default this satisfies all kind='archive' requirements after verifying the real ZIP. Run completion_check after export completes.

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>",
      "op_id": "<op_id>"
    },
    "name": "project_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
task_idYes
revisionYes
requirement_idsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare mutation/destructive/idempotent flags; the description adds genuinely new behavioral facts: the call is asynchronous and returns operation_id immediately, a lease must be released before waiting, and the archive lands outside project_path so its absolute path must not be registered as a project file. That lease-management and path-placement guidance is exactly the context annotations cannot convey.

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?

Content is front-loaded with purpose, then async behavior, then downstream routing, with no filler sentences. A few sentences are terse to the point of being cryptic (release the lease before waiting), but each carries operational weight.

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?

An output schema exists so return values need not be explained, and async/lease/routing behavior is well covered. However, the tool is marked destructiveHint=true and idempotent while the description never says what is written or whether an existing archive is overwritten, and the five parameters remain unexplained — meaningful gaps for a mutating, multi-parameter operation.

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% across five parameters, so the description carries the full burden of explaining semantics. It mentions lease release and requirement satisfaction, which hints at token and requirement_ids, but gives no meaning for task_id, revision, op_id, or requirement_ids explicitly, leaving most parameters undocumented in both places.

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

Purpose5/5

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

States a specific verb (Export) and enumerates the concrete payload (project files, original request, results, history, rules, job accounting, continuation instructions) plus the output format (ZIP). It is clearly distinguishable from project_import and operation_get by what it produces versus what those siblings do with or report on the archive.

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

Usage Guidelines5/5

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

Explicit sequencing rules are given: release the lease before waiting, use operation_get to retrieve the archive path/hash, run completion_check after export completes, and another task may pass the ZIP to project_import. It also states the archive satisfies all kind='archive' requirements by default, which tells the agent when this tool is the right call.

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