Skip to main content
Glama

skillporter_install

Install a local workspace skill directory into target harnesses using copy or symlink, with writes enabled only when SKILLPORTER_MCP_ALLOW_WRITES=1.

Instructions

[WRITE] Install a local workspace skill directory into target 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": {
      "skill": "<skill>",
      "harnesses": "<harnesses>"
    },
    "name": "skillporter_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
forceNo
skillYesWorkspace-relative path to skill directory
strategyNocopy
harnessesYes
accept_riskNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already mark this as a non-read-only, non-destructive operation; the description adds the valuable detail that writes are gated behind an environment variable, which is not in structured fields. It does not explain what happens to existing files in target harnesses, whether force overwrites, or whether the operation is reversible.

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?

A single front-loaded sentence with the [WRITE] marker first and the gating condition last; no wasted words. It is terse to the point of under-specification, but the structure itself is sound.

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?

For a six-parameter mutation tool with no output schema and very low schema coverage, the definition is too thin: side effects on target harnesses, the meaning of force/strategy/accept_risk, and the outcome of the install are all unaddressed. The write-gate note helps but does not compensate.

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?

With six parameters and only 17% schema description coverage, the description carries most of the burden but says nothing about path, force, strategy, harnesses, or accept_risk. In particular, the copy-vs-symlink strategy enum and the safety-implying accept_risk flag are left entirely unexplained.

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?

The description states a specific verb+resource: installing a local workspace skill directory into target harnesses. It is clearly a write/install operation distinct from read-oriented siblings such as inspect or status, though it does not explicitly distinguish itself from add, import, or sync.

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?

It gives an invocation prerequisite (SKILLPORTER_MCP_ALLOW_WRITES=1) and the implicit condition that the skill must be a local workspace directory. However, it offers no routing guidance against close siblings like add, import, or sync, so the agent must infer when this is the right choice.

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