Skip to main content
Glama
ihorponom

agentpack

by ihorponom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bundle_export

Export a task passport as a redacted JSON bundle for sharing across repos, machines, or agents. Includes decisions, dead ends, source conclusions, and optional evidence, without altering pack state.

Instructions

Export one Task Passport with its decisions, dead ends, source conclusions, and optionally evidence to a redacted agentpack.task-bundle JSON file, for sharing tasks across repos, machines, or agents. Writes only the new bundle file at outputPath; pack state is unchanged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdNoTask Passport id to export. Defaults to the current task.
sourcesNoRepo-relative source paths whose Source Cache records to include.
outputPathYesDestination bundle file: must be a new repo-relative path outside .agentpack/ and .git/; existing files and symlink escapes are rejected.
includeEvidenceNoInclude referenced evidence file contents. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.4.0
    • 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."
  2. First observedv1.3.0

TDQS

A4.5/5.0
Behavior5/5

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

The description reveals that the tool writes only a new bundle file and leaves pack state unchanged, which is critical side-effect information given all annotation hints are false. It also mentions the output is 'redacted,' adding behavioral nuance.

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?

Two sentences. The first establishes purpose and scope; the second clarifies the side-effect boundary. No redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 params, full schema coverage, and no output schema, the description adequately covers purpose, output, and side effects. It's sufficient for an agent to select and invoke the tool.

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 covers all 4 parameters with descriptions (100% coverage). The tool description itself doesn't add parameter details beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the tool exports one Task Passport with decisions, dead ends, source conclusions, and optionally evidence to a redacted agentpack.task-bundle JSON file. It distinguishes from siblings like bundle_inspect (inspect) and bundle_import (import) by specifying the export action and sharing purpose.

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?

The description provides clear context: 'for sharing tasks across repos, machines, or agents.' It doesn't explicitly name alternatives or exclusions, but the context is sufficient to infer when to use it.

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