MCP X-Platform

Overview Schema Source Related Servers Discussions Admin

analyze_shell_commands

Analyze shell scripts for cross-platform compatibility issues, detecting platform-specific commands and environment variable problems across Linux, macOS, and Windows.

Instructions

Analyze shell commands and scripts for cross-platform compatibility

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

Input Schema

Name	Required	Description
`path`	Yes	Directory or file path to analyze
`checkEnvVars`	No	Check environment variable usage
`targetShells`	No	Target shell environments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden. It only states the function without disclosing behavioral traits like whether it is read-only, whether it modifies files, performance implications, or what kind of output is produced.

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

Conciseness5/5

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

The description is a single, direct sentence with no filler. It is appropriately front-loaded and concise.

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 lack of annotations and no output schema, the description is insufficient. It does not describe what the tool returns (e.g., a report, list of issues) or any side effects, leaving the agent without complete information to understand the tool's full behavior.

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

Parameters3/5

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

Schema coverage is 100%, so the input schema already fully describes each parameter. The description adds no additional meaning beyond what the schema provides, meeting the baseline expectation.

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 identifies the tool's purpose: analyzing shell commands and scripts for cross-platform compatibility. The verb 'analyze' and resource 'shell commands and scripts' are specific, and it distinguishes itself from sibling tools that focus on build systems, dependencies, file paths, etc.

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?

The description provides no guidance on when to use this tool versus alternatives. Siblings like analyze_build_systems or detect_platform_apis are listed but not differentiated in terms of usage context.

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

Deploy Server