Skip to main content
Glama

skillporter_sync

Synchronize agent workspace skills across target harnesses to keep copies consistent; enable write access with SKILLPORTER_MCP_ALLOW_WRITES=1.

Instructions

[WRITE] Synchronize workspace skills across target harnesses (requires SKILLPORTER_MCP_ALLOW_WRITES=1).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "skillporter_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
forceNo
strategyNocopy
harnessesNo
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 declare readOnlyHint=false and destructiveHint=false, so the description's '[WRITE]' marker is largely redundant with structured data. It does add genuinely new context with the SKILLPORTER_MCP_ALLOW_WRITES=1 gate, which an agent needs before attempting a call, but it says nothing about what files are created or overwritten, whether sync is reversible, or how the force/accept_risk parameters alter risk.

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 and prerequisite in parentheses, with no filler. It is efficiently structured, though the terseness comes at the cost of the parameter and behavioral detail noted elsewhere.

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?

This is a five-parameter write operation with no output schema and zero schema coverage, and the description supplies only one sentence. For a mutation tool with a strategy enum, a force flag, and an accept_risk flag, the definition leaves far too much for the agent to infer before invoking it safely.

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 0% across five parameters, so the description carries the full burden and mostly fails it. Only 'target harnesses' loosely maps to the harnesses array; path, strategy (copy vs symlink), force, and especially accept_risk are left entirely unexplained, and the risk-related flags are exactly the ones an agent most needs described.

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 uses a specific verb+resource ('Synchronize workspace skills') and names the scope ('across target harnesses'), which tells an agent this is a mutation-style sync operation. It falls short of a 5 because it does not contrast itself with sibling tools like skillporter_preview, skillporter_diff, or skillporter_consolidate_preview that an agent would plausibly confuse it with.

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?

Usage is only implied: 'Synchronize ... across target harnesses' suggests when the tool applies, and the env-var prerequisite is a useful gating condition. However, there is no explicit when-not guidance, no mention of a preview/diff alternative to run first, and no explanation of when to choose this over skillporter_preview or skillporter_import.

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