Skip to main content
Glama
posidron

PowerShell MCP Server

by posidron

get_command_help

Retrieve detailed help for any PowerShell command to understand its usage, parameters, and examples. Simplify command execution and management on Windows systems.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesPowerShell command to get help for

Implementation Reference

  • Handler function that retrieves detailed help for a PowerShell command using Get-Help -Full, structures the output as JSON, executes via powershell command, and returns markdown content or error.
    async ({ command }: { command: string }) => {
      try {
        const psCommand = `
          $Help = Get-Help ${command} -Full
          $Output = [PSCustomObject]@{
            Name = $Help.Name
            Synopsis = $Help.Synopsis
            Syntax = $Help.Syntax | Out-String
            Description = $Help.Description | Out-String
            Parameters = $Help.Parameters.Parameter | ForEach-Object {
              [PSCustomObject]@{
                Name = $_.Name
                Type = $_.Type.Name
                Required = $_.Required
                Description = $_.Description | Out-String
              }
            }
            Examples = $Help.Examples.Example | ForEach-Object {
              [PSCustomObject]@{
                Title = $_.Title
                Code = $_.Code
                Remarks = $_.Remarks | Out-String
              }
            }
          }
          ConvertTo-Json -InputObject $Output -Depth 5
        `;
    
        const { stdout, stderr } = await execAsync(
          `powershell -Command "${psCommand.replace(/"/g, '\\"')}"`
        );
    
        if (stderr) {
          return {
            isError: true,
            content: [
              {
                type: 'text' as const,
                text: `Error retrieving help: ${stderr}`,
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: 'text' as const,
              text: stdout,
            },
          ],
        };
      } catch (error) {
        return {
          isError: true,
          content: [
            {
              type: 'text' as const,
              text: `Error retrieving help: ${(error as Error).message}`,
            },
          ],
        };
      }
    }
  • Input schema using Zod: requires a 'command' string parameter describing the PowerShell command to get help for.
    {
      command: z.string().describe('PowerShell command to get help for'),
    },
  • src/index.ts:188-257 (registration)
    Tool registration call: this.server.tool('get_command_help', schema, handler) within the registerTools method.
    this.server.tool(
      'get_command_help',
      {
        command: z.string().describe('PowerShell command to get help for'),
      },
      async ({ command }: { command: string }) => {
        try {
          const psCommand = `
            $Help = Get-Help ${command} -Full
            $Output = [PSCustomObject]@{
              Name = $Help.Name
              Synopsis = $Help.Synopsis
              Syntax = $Help.Syntax | Out-String
              Description = $Help.Description | Out-String
              Parameters = $Help.Parameters.Parameter | ForEach-Object {
                [PSCustomObject]@{
                  Name = $_.Name
                  Type = $_.Type.Name
                  Required = $_.Required
                  Description = $_.Description | Out-String
                }
              }
              Examples = $Help.Examples.Example | ForEach-Object {
                [PSCustomObject]@{
                  Title = $_.Title
                  Code = $_.Code
                  Remarks = $_.Remarks | Out-String
                }
              }
            }
            ConvertTo-Json -InputObject $Output -Depth 5
          `;
    
          const { stdout, stderr } = await execAsync(
            `powershell -Command "${psCommand.replace(/"/g, '\\"')}"`
          );
    
          if (stderr) {
            return {
              isError: true,
              content: [
                {
                  type: 'text' as const,
                  text: `Error retrieving help: ${stderr}`,
                },
              ],
            };
          }
    
          return {
            content: [
              {
                type: 'text' as const,
                text: stdout,
              },
            ],
          };
        } catch (error) {
          return {
            isError: true,
            content: [
              {
                type: 'text' as const,
                text: `Error retrieving help: ${(error as Error).message}`,
              },
            ],
          };
        }
      }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/posidron/mcp-powershell'

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