Skip to main content
Glama

desktop_skills_get

Fetches a named Desktop Pilot skill guide as Markdown, with optional reference file or full reference output, to support desktop automation workflows.

Instructions

agent-desktop skills get: Print a skill (markdown in data.content)

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

Input Schema

NameRequiredDescriptionDefault
fullNoAppend every reference file to the output
nameYesSkill name or alias: desktop, platform, macos, windows, linux, ffi, jev
referenceNoReference filename (e.g. workflows or references/workflows.md). Omit for the main guide.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add useful context by stating the output is markdown surfaced in data.content, but it never explicitly confirms the operation is read-only, nor explains how 'full' and 'reference' interact with what gets printed, or what happens for an unknown skill name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded, which is good, but the leading 'agent-desktop skills get:' merely restates the tool name and wastes space. The remainder is efficient but so terse it under-specifies the tool rather than being genuinely concise.

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?

For a simple three-parameter read tool with full schema coverage and no output schema, the description is minimally adequate. It mentions the return channel (data.content) but leaves behavioral details about the reference/full combination and error handling to inference.

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%, so all three parameters are documented (name with alias examples, reference filename, full flag). The description adds no meaning beyond that, which is acceptable given the schema already does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Print/Get) and resource (a skill), and hints at the return location (markdown in data.content). However, the purpose is vague about what a 'skill' is in this context, and it does not distinguish this retrieval tool from siblings like desktop_skills_list or desktop_skills_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?

Provides no when-to-use or when-not-to-use guidance and never names an alternative. The agent must infer that this fetches a specific skill's content, while desktop_skills_list enumerates skills and desktop_skills_path returns a path, without any help from the description.

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