Skip to main content
Glama

Bundle dependencies (self-contained package)

bundle_dependencies
Destructive

Make a component self-contained by scanning external references, copying assets, rewriting network parameters to relative paths, and saving a portable .tox package.

Instructions

Make a COMP self-contained: recursively scan its subtree for external file references (movie/image files, fonts, LUTs, externaltox links — reusing the collect_project_assets scan), COPY each existing asset into /assets/, rewrite each referencing parameter in the LIVE network to the copied relative path (assets/), then save the COMP as a .tox beside its assets with a tdmcp-component manifest. The result is a folder you can move to another machine and open without broken links. Delta vs make_portable_tox (which saves the .tox only, leaving external assets behind) and collect_project_assets (which only reports refs). Rewriting mutates the live network — set rewrite_refs=false to copy-and-report without touching parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPackage/.tox stem. Defaults to the last path segment of comp_path.
out_dirYesLocal folder to write the self-contained package into (created if missing). The .tox and an assets/ subfolder land here.
comp_pathYesFull path of the COMP subtree to bundle (assets are gathered recursively).
rewrite_refsNoWhen true, rewrite each referencing parameter in the LIVE network to the copied relative path (assets/<file>) BEFORE saving the .tox, so the saved component points at the bundled copies. When false, assets are copied but the network is left untouched (a report-and-copy pass).
include_missingNoIf true, still record assets whose source file is missing on disk (they cannot be copied and their ref is not rewritten). If false, missing refs are skipped with a warning.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
compYesEchoed COMP path that was bundled.
out_dirYesAbsolute package folder.
skippedYesRefs that were not bundled (missing source, or duplicate collision).
tox_pathYesAbsolute path of the saved .tox.
warningsYes
tox_bytesYesSize of the saved .tox in bytes, or null if unknown.
copied_countYes
assets_copiedYesEvery external file that was copied into the package.
manifest_pathYesAbsolute path of the tdmcp-component.json manifest written.
Behavior5/5

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

Annotations declare destructiveHint=true, and the description adds valuable details: 'Rewriting mutates the live network' and explains the rewiring process. The ability to avoid mutation via rewrite_refs=false is clearly stated, surpassing the basic annotation.

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?

The description is front-loaded with the main action, then a clear step-by-step breakdown, followed by sibling comparison and a behavioral warning. Every sentence adds value, and the structure is logical without redundancy.

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 the tool's complexity (scan, copy, rewrite, save), the description covers all essential aspects: purpose, workflow, parameter roles, side effects, and alternatives. The output schema is present, so return value details are not needed. Comprehensive for an agent.

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

Parameters5/5

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

Schema coverage is 100% with parameter descriptions, but the description enriches understanding by contextualizing each parameter within the workflow. For example, rewrite_refs is explained in terms of its impact on live network mutation, and include_missing is clarified with behavior when missing files.

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's purpose: to make a COMP self-contained by recursively scanning, copying assets, rewriting references, and saving as a .tox with manifest. It explicitly distinguishes from siblings make_portable_tox and collect_project_assets, providing a precise verb+resource+scope.

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?

The description explicitly provides when-use guidance by contrasting with sibling tools: 'Delta vs make_portable_tox (which saves the .tox only, leaving external assets behind) and collect_project_assets (which only reports refs).' It also notes the mutative behavior and the option to set rewrite_refs=false for a non-destructive run.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server