agentpack

Overview Schema Source Related Servers Discussions Admin

bundle_export

Export one Task Passport, compact handoff, latest task checkpoint when available, selected source conclusions, and optionally referenced evidence to a redacted agentpack.task-bundle JSON file.

Instructions

Export one Task Passport, compact handoff, latest task checkpoint when available, selected source conclusions, and optionally referenced evidence to a redacted agentpack.task-bundle JSON file. Writes only the new bundle file at outputPath; pack state is unchanged.

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": {
      "outputPath": "<outputPath>"
    },
    "name": "bundle_export"
  }
}

Input Schema

Name	Required	Description
`taskId`	No	Task Passport id to export. Defaults to the current task.
`sources`	No	Repo-relative source paths whose Source Cache records to include.
`outputPath`	Yes	Destination bundle file: must be a new repo-relative path outside .agentpack/ and .git/; existing files and symlink escapes are rejected.
`includeEvidence`	No	Include referenced evidence file contents. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.4.0Jul 10, 2026

addedInput schema / properties / includeEvidence / description

Added value: +"Include referenced evidence file contents. Defaults to true."

addedInput schema / properties / outputPath / description

Added value: +"Destination bundle file: must be a new repo-relative path outside .agentpack/ and .git/; existing files and symlink escapes are rejected."

addedInput schema / properties / sources / description

Added value: +"Repo-relative source paths whose Source Cache records to include."

addedInput schema / properties / taskId / description

Added value: +"Task Passport id to export. Defaults to the current task."

First observedv1.3.0Jul 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description reinforces this by clarifying that only the new bundle file is written and 'pack state is unchanged'. That is genuinely useful context beyond the annotation flags, though it does not cover auth needs or overwrite/error behavior.

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 dense but efficient sentences, with the export contents front-loaded before the write-behavior caveat. Every clause earns its place; slightly long enumeration is the only cost.

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?

For a no-output-schema export tool, the description covers what is written, where, and that pack state is untouched, which is sufficient for correct invocation. Minor omissions like overwrite/error semantics are already handled by the schema's outputPath description.

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 100%, so the schema already documents all four parameters, including the outputPath constraints and includeEvidence default. The description adds 'at outputPath' and 'optionally referenced evidence' but no syntax or format detail beyond the schema, so the baseline 3 applies.

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 exact resources bundled (Task Passport, handoff, checkpoint, source conclusions, evidence) plus the output artifact (redacted agentpack.task-bundle JSON file). An agent can distinguish this from bundle_inspect and bundle_import without opening any schema.

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?

Conveys what gets exported and where it is written, implying a 'produce a shareable bundle' use case, but never states when to choose this over bundle_inspect or bundle_import. No explicit alternatives or prerequisites are given, so usage is only implied.

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