Skip to main content
Glama
wonderwhy-er

Claude Desktop Commander MCP

by wonderwhy-er
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

get_prompts

Read-only

Fetch and run a predefined onboarding prompt to automate tasks such as folder organization, codebase analysis, knowledge base creation, data file analysis, or system health checks.

Instructions

                    Retrieve a specific Desktop Commander onboarding prompt by ID and execute it.
                    
                    SIMPLIFIED ONBOARDING V2: This tool only supports direct prompt retrieval.
                    The onboarding system presents 5 options as a simple numbered list:
                    
                    1. Organize my Downloads folder (promptId: 'onb2_01')
                    2. Explain a codebase or repository (promptId: 'onb2_02')
                    3. Create organized knowledge base (promptId: 'onb2_03')
                    4. Analyze a data file (promptId: 'onb2_04')
                    5. Check system health and resources (promptId: 'onb2_05')
                    
                    USAGE:
                    When user says "1", "2", "3", "4", or "5" from onboarding:
                    - "1" → get_prompts(action='get_prompt', promptId='onb2_01')
                    - "2" → get_prompts(action='get_prompt', promptId='onb2_02')
                    - "3" → get_prompts(action='get_prompt', promptId='onb2_03')
                    - "4" → get_prompts(action='get_prompt', promptId='onb2_04')
                    - "5" → get_prompts(action='get_prompt', promptId='onb2_05')
                    
                    The prompt content will be injected and execution begins immediately.

                    This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
promptIdYes

Tool Definition Quality

A3.7/5.0
Behavior1/5

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

The description states 'execution begins immediately', indicating a write/mutation behavior, but annotations mark it as readOnlyHint=true. This is a clear contradiction, so score is 1 per guidelines.

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?

The description is well-structured with sections, front-loaded purpose, and concise usage table. It is longer but each part adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 2 params and no output schema, the description provides sufficient context for the intended onboarding use case. It explains the mapping and immediate execution, though it does not specify return values.

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?

Schema coverage is 0%, but the description adds explicit valid values for promptId and the fixed action enum, going beyond the minimal schema definition.

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

Purpose5/5

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

The description clearly states the verb 'retrieve and execute' and the resource 'specific Desktop Commander onboarding prompt by ID'. It distinguishes itself from sibling tools (file/process tools) by focusing on onboarding prompt retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit usage with a numbered mapping for user input to promptId. It also mentions the simplified onboarding context and how to reference the command. However, it does not directly exclude alternatives or state when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wonderwhy-er/DesktopCommanderMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server