MCP X-Platform

by Atomic-Germ

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

analyze_dependencies

Analyze dependencies to identify platform-specific package compatibility issues across Windows, macOS, and Linux.

Instructions

Analyze dependencies for platform-specific packages and 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_dependencies"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Project root path
`platforms`	No	Target platforms to validate against
`checkArchitecture`	No	Check architecture-specific dependencies
`checkNativeModules`	No	Check for native/binary dependencies

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only states 'Analyze dependencies...' without revealing whether it modifies state, what output to expect, or any side effects. This is insufficient for a tool with 4 parameters.

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 a concise single sentence with no filler. It could be slightly improved by adding more context while remaining succinct, but overall it is efficient.

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 4 parameters and no output schema or annotations, the description is incomplete. It does not explain what the tool returns, error conditions, or the scope of analysis, which is needed for safe invocation.

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?

All 4 parameters are described in the input schema (100% coverage), so the description adds no extra meaning. Baseline score of 3 applies as the schema already explains each parameter's purpose.

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?

The description clearly states it analyzes dependencies for platform-specific packages and compatibility, using specific verb and resource. However, it does not distinguish it from sibling tools like analyze_build_systems, which also deal with dependencies.

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, nor any context about when not to use it. Usage is only implied by the action 'analyze dependencies'.

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

Deploy Server