npm-mcp

pack

Create a tarball from a local package directory to preview files that would be published to npm. Optionally dry-run to list files without creating a tarball.

Instructions

Create a tarball from a package (preview what would be published)

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": {
      "path": "<path>"
    },
    "name": "pack"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute path to the package directory
`dryRun`	No	List files without creating tarball

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Mar 19, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions creating a tarball but does not explain side effects (e.g., where the file is saved, whether it overwrites existing files) or required permissions. The 'preview' hint is vague without elaboration on default behavior when dryRun is false.

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 a single, concise sentence that front-loads the core action and includes a clarifying parenthetical. Every word serves a purpose, with no unnecessary detail.

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

Completeness2/5

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

Given the simplicity of the tool (2 parameters, no output schema), the description fails to cover important context such as output file location, error scenarios, or default behavior. The 'preview' hint is insufficient for complete understanding.

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?

The input schema has 100% coverage with descriptions for both parameters ('path' and 'dryRun'). The description adds no additional meaning beyond what the schema already provides, so it meets the baseline expectation.

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: 'Create a tarball from a package (preview what would be published)'. It uses a specific verb ('Create') and resource ('tarball from a package'), and the parenthetical distinguishes it from publishing, differentiating from sibling tools like 'publish'.

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?

The description implies usage for previewing before publishing via the parenthetical, but it does not explicitly state when to use this tool over alternatives (e.g., 'publish' or 'pack' with dryRun). No conditional guidance or exclusions are provided.

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

Deploy Server