Skip to main content
Glama

skillporter_preview

Read-only

Preview the exact rule content a target harness receives for a workspace skill, including translation limitations, to verify how skills adapt before use.

Instructions

[READ] Preview the exact native or adapted rule content a target harness receives for a workspace skill, including any translation limitations.

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": {
      "target": "<target>",
      "harness": "<harness>"
    },
    "name": "skillporter_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
targetYesWorkspace-relative skill path or installed skill name
harnessYesTarget harness ID (e.g. cursor, github-copilot, aider)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, and the '[READ]' prefix merely restates that. The description does add real behavioral content beyond the annotation by saying the output may be 'adapted' and may carry 'translation limitations', which tells the agent the preview can show lossy conversions. It says nothing about permissions, workspace resolution, or failure modes for an unknown harness.

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?

A single front-loaded sentence with the read-only tag first and the payload scope second; no padding or repetition. Every clause contributes (preview, content nature, target, limitations).

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

Completeness3/5

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

With no output schema, the description does carry the return-value burden and does so adequately by naming 'rule content' and noting adaptation/limitations. However, for a 3-parameter tool where one parameter is undocumented in both schema and description, and with no guidance on which harness IDs are valid, the definition is only minimally complete.

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 67%, and the uncovered parameter is 'path', which has no description at all beyond a default of '.'. The description adds no parameter-level meaning: it does not clarify what 'target' resolves to (path vs installed name), what harness IDs are valid, or how 'path' relates to 'target'. It leaves the one undocumented parameter completely 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 names a specific verb (preview) and resource (the native or adapted rule content a target harness receives for a workspace skill), plus a scope detail (translation limitations). It is distinguishable from inspect/diff/export in spirit, but it never names or contrasts a sibling, so the 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 Guidelines3/5

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

Usage is only implied: a 'preview' of what a harness receives suggests checking output before an export/sync, but the description never states when to use this versus skillporter_diff, skillporter_inspect, or skillporter_export, nor any preconditions. Clear enough to guess intent, not enough to route reliably.

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