Skip to main content
Glama

skillporter_detect

Read-only

Detects installed or active AI coding and autonomous agent harnesses in a workspace, helping you assess harness coverage before auditing skills.

Instructions

[READ] Detect which AI coding and autonomous agent harnesses are installed or active.

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

Input Schema

NameRequiredDescriptionDefault
pathNoWorkspace-relative path (default: '.')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotation already declares readOnlyHint=true, so the "[READ]" prefix is largely redundant. The description adds no behavior beyond that: it does not say what detection inspects (filesystem, config files, running processes), how expensive the call is, or what happens if the path does not exist. With annotations covering safety only, the description leaves the operational behavior opaque.

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?

It is a single front-loaded sentence with no filler, and the read-only marker is placed first. Its brevity is efficient, though it borders on under-specification rather than deliberate concision.

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?

There is no output schema, so the description carries the burden of explaining what a detection result looks like, and it does not. It never says whether the response lists harness names, versions, active/inactive state, or detected config paths, which is the key information an agent needs to use the result.

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?

Schema description coverage is 100% and the single path parameter is already documented, so the baseline of 3 applies. The description never mentions the path argument or what scope the default '.' implies, so it adds no meaning beyond the schema.

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 gives a specific verb ("Detect") and a concrete resource ("AI coding and autonomous agent harnesses"), with the additional qualifier "installed or active" that narrows the scope. It is clearly distinguishable from siblings like install, remove, or sync, though it does not explicitly contrast with close-sounding siblings such as scan, inspect, or status.

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?

There is no when-to-use or when-not-to-use guidance beyond the "[READ]" tag, which only signals that the call is non-mutating. Nothing tells the agent whether to prefer this over skillporter_scan or skillporter_status, or under what conditions detection is the right first step.

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