Skip to main content
Glama
wonderwhy-er

Claude Desktop Commander MCP

by wonderwhy-er
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

get_prompts

Read-only

Retrieve a Desktop Commander onboarding prompt by ID and execute it to automate tasks like organizing files, analyzing data, or checking system resources.

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.5/5.0
Behavior1/5

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

The annotation declares readOnlyHint: true, but the description states 'retrieve and execute it', implying execution with potential side effects. This is a clear contradiction. No further behavioral details are provided beyond the contradictory execution claim.

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?

The description is well-structured with sections and clear formatting, but it is somewhat verbose. It could be more concise while retaining essential information.

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?

The description covers usage and parameter values adequately, but lacks details about return values, error handling, and what 'execution begins immediately' means. Given no output schema, the agent might be left uncertain about results.

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%, so the description must compensate. It does so by listing all valid prompt IDs mapped to numbers and specifying the action enum value. This adds meaning beyond the schema's bare string definitions.

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 tool retrieves and executes a specific Desktop Commander onboarding prompt by ID. It distinguishes from sibling tools by focusing exclusively on onboarding prompts and providing a direct numbered list.

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?

The description provides explicit mapping from user selections (1-5) to prompt IDs and the action parameter. It effectively tells the agent when to use this tool during onboarding. However, it does not explicitly state when not to use it or mention alternative tools.

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