OmniCommanderMCP

by kaannsaydamm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

windows_registry

Read, write, or delete Windows registry keys and values using PowerShell commands.

Instructions

Windows-only registry query/set/delete through PowerShell.

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": {
      "operation": "<operation>",
      "path": "<path>"
    },
    "name": "windows_registry"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`path`	Yes
`value`	No
`operation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations provided; description only mentions 'through PowerShell' without detailing permissions (admin required), side effects, or error behavior. Minimal behavioral insight beyond basic action.

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?

Description is very concise (one sentence, 6 words) and front-loaded, but it is too brief for a registry tool with multiple operations. Every word earns its place, but the sentence could be expanded to cover essential context.

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

Completeness2/5

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

Given the complexity and potential danger of registry operations, the description omits critical context: path syntax, required permissions, error handling, and return values. Incomplete for safe and correct usage.

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

Parameters2/5

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

Schema description coverage is 0%, but description fails to explain parameters (path, name, value) beyond operation. Agent gets no guidance on how to structure path or when name/value are required.

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?

Description clearly states the tool operates on Windows registry with actions query/set/delete via PowerShell, distinguishing it from sibling tools which are general system utilities. However, it could specify the registry path format (e.g., HKLM\...).

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?

No guidance on when to use this tool vs alternatives; no mention of prerequisites, security context, or conditions. Agent lacks context for appropriate invocation.

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