Skip to main content
Glama

skillporter_import

Destructive

Validates and restores a workspace-relative .skillpack archive into selected harnesses; supports dry-run previews and force overwrites when required.

Instructions

[WRITE] Validate and restore a workspace-relative .skillpack archive into selected harnesses (requires SKILLPORTER_MCP_ALLOW_WRITES=1).

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

Input Schema

NameRequiredDescriptionDefault
packYesWorkspace-relative path to .skillpack archive
pathNo.
forceNo
dry_runNo
harnessesNo
accept_riskNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered structurally. The description genuinely adds the write-gate prerequisite (SKILLPORTER_MCP_ALLOW_WRITES=1) and mentions a validation step, which is useful context. However, it never explains overwrite behavior with force, the effect of accept_risk, or whether a dry_run path exists, which is a notable gap for a destructive tool.

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?

One sentence, front-loaded with the [WRITE] marker that is the most decision-relevant token, then purpose, then the gating condition. Nothing is wasted.

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?

A six-parameter destructive write tool with low schema coverage and no output schema needs far more than one sentence. The description omits the semantics of four parameters, any statement about what existing state is replaced, and what a successful restore returns or reports.

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

Parameters2/5

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

Schema description coverage is only 17%, so the description must compensate and does not. Only "pack" is echoed (workspace-relative path to .skillpack archive) and "harnesses" is loosely referenced; path, force, dry_run, and accept_risk receive no explanation at all, leaving a destructive write tool's most consequential flags undocumented.

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

Purpose4/5

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

"Validate and restore a workspace-relative .skillpack archive into selected harnesses" gives a specific verb pair and resource with scope. It implies a distinction from siblings like skillporter_install or skillporter_export, but never names one, so differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no comparison against alternatives such as skillporter_install, skillporter_preview, or skillporter_inspect. "Into selected harnesses" hints at the targeting parameter but does not tell the agent when import is the right call versus another sibling.

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