Skip to main content
Glama

skillporter_suggest

Read-only

Analyze local project manifests and configuration without uploads to recommend relevant, security-graded skills for your workspace.

Instructions

[READ] Analyze local project manifests and configuration (100% local, zero uploads) and recommend relevant, security-graded skills.

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_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.

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=true, so the description need not re-establish safety. It does add genuinely new context — '100% local, zero uploads' — which tells the agent no network transmission occurs, but it says nothing about what 'security-graded' means, how grading is determined, or what the recommendation output contains.

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?

One compact sentence with the strongest qualifier (locality/privacy) placed inline rather than buried. Nothing is redundant, though the '[READ]' tag partially duplicates the readOnlyHint annotation.

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?

A low-complexity, single-parameter tool with no output schema, so the description has a modest burden. It covers the what and the privacy posture but leaves the path parameter's meaning and the shape of the recommendation entirely unspecified.

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% and the single 'path' parameter has only a default of '.'. The description mentions 'local project' but never clarifies that path selects the directory to analyze, whether it accepts relative or absolute paths, or what happens when it is omitted.

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 pair ('Analyze ... and recommend') and resource ('local project manifests and configuration'), plus the nature of the output ('security-graded skills'). It is clear what the tool produces, though it does not explicitly distinguish itself from similarly-named siblings like skillporter_scan or skillporter_detect.

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 and no named alternatives. The '[READ]' prefix and 'zero uploads' note imply this is a safe, non-mutating entry point, but the agent gets no signal about when to pick this over scan, detect, or inspect.

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