Skip to main content
Glama

skillporter_inspect

Read-only

Inspect a workspace or remote skill package to verify its structure, metadata, and security posture before auditing AI agent skills.

Instructions

[READ] Inspect a workspace or remote skill package structure, metadata, and security posture.

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": {
      "source": "<source>"
    },
    "name": "skillporter_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesWorkspace-relative path or remote skill specifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the "[READ]" tag merely restates it. The description does add scope context by enumerating what is inspected (structure, metadata, security posture), but says nothing about output shape, depth, or whether remote fetches have side effects or network requirements.

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 no filler, and the key facets are listed compactly. The "[READ]" prefix is redundant with the readOnlyHint annotation, a minor waste.

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

Completeness4/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 carries the burden of indicating what comes back, and it does so by naming structure, metadata, and security posture. For a one-parameter read tool this is close to sufficient, though it omits any note on result depth or remote-source behavior.

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?

Only one parameter with 100% schema description coverage, so the schema already explains that source accepts a workspace-relative path or remote specifier. The description's "workspace or remote" phrasing echoes that without adding format examples or validation rules; baseline 3 applies.

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?

States a specific verb ("Inspect") and resource ("workspace or remote skill package") plus the facets examined: structure, metadata, and security posture. It does not name or contrast with any sibling (e.g., scan, detect, diagnose), so an agent must infer differentiation from names alone.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as skillporter_scan or skillporter_diagnose. The "[READ]" prefix hints at a read-only inspection step but does not say when this tool 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.