Skip to main content
Glama

desktop_skills_list

Lists bundled agent-desktop skills with summaries, helping you discover available capabilities and choose the right skill for a task.

Instructions

agent-desktop skills list: List bundled skills with summaries (default)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. "List" implies a read-only operation and the word "summaries" hints at abbreviated records, but nothing states the return shape, whether paths or metadata are included, or whether errors can occur. Two words of behavioral signal are not enough for an unannotated tool.

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 short line that is front-loaded with the action. The "agent-desktop skills list:" prefix is redundant with the tool name and consumes space that could have gone toward differentiating this from its siblings.

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 zero-parameter listing tool with no output schema this is barely adequate: it says what is listed (bundled skills) and what is returned (summaries). It omits how to move from a summary to full detail via desktop_skills_get, which the agent would need to know in a two-step workflow.

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 zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. "(default)" is the only qualifier and does not add parameter meaning.

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: "List bundled skills with summaries." The "agent-desktop skills list:" prefix largely restates the tool name, and it does not distinguish the output from siblings such as desktop_skills_get, so it falls short of the top mark.

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?

Aside from the "(default)" tag, there is no guidance on when to call this tool rather than desktop_skills_get or desktop_skills_path. The agent must infer that this is the overview listing and that the others fetch detail or paths.

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