Skip to main content
Glama

desktop_skills_path

Prints the directory path where bundled Desktop Pilot skills are stored so you can locate and inspect skill files.

Instructions

agent-desktop skills path: Print where bundled skills live

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": "desktop_skills_path"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. "Print" implies a non-mutating read that returns a location, which is a reasonable inference for a zero-parameter tool, but the description does not state the return format or whether the path is always defined. For a trivially safe read, this is adequate but thin.

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 short, front-loaded sentence with no filler. The "agent-desktop skills path:" prefix simply restates the tool name, which is minor redundancy, but nothing else is wasted.

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?

Given a zero-parameter call with no output schema, the description should ideally say what the printed value is and when it is useful. It conveys the gist (bundled skills location) but leaves the return semantics and the choice against sibling skills tools implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is no schema semantics for the description to add. The baseline of 4 applies; nothing is missing on this dimension.

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 states a specific verb and resource: "Print where bundled skills live." That distinguishes it from the sibling operations desktop_skills_list and desktop_skills_get, which surface skill content rather than the storage location. It is clear, though the phrasing is informal rather than precise about what the output is (a filesystem path).

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 guidance on when to call this rather than desktop_skills_list or desktop_skills_get, no prerequisites, and no exclusions. An agent must infer that this is for locating skill files on disk instead of reading them.

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