Skip to main content
Glama
Sign In
MCP X-Platform

MCP X-Platform

by Atomic-Germ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_build_systems

Analyzes build configurations to identify cross-platform incompatibilities in supported build tools and scripts.

Instructions

Analyze build system configurations 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_build_systems"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesProject root path
buildToolsNoBuild tools to analyze
checkScriptsNoCheck build scripts for platform issues

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose whether the tool is read-only, requires permissions, or what the output format is. The brief description gives no behavioral context beyond the core function.

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 single concise sentence that efficiently conveys the tool's core purpose. It is front-loaded with the key action and target, but some additional context (e.g., output format) could be added without sacrificing conciseness.

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?

Despite having 3 parameters and no output schema, the description does not explain what the analysis produces, how to interpret results, or any prerequisites. This is insufficient for an agent to fully understand the tool's behavior and outputs.

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?

The input schema descriptions cover all 3 parameters (100% coverage) with clear explanations. The tool description adds no additional parameter meaning beyond the schema, so it meets the baseline expectation but does not exceed it.

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 the verb 'Analyze' and the resource 'build system configurations' with the purpose of 'cross-platform compatibility'. It distinguishes this tool from sibling tools like analyze_dependencies and analyze_file_paths by focusing on build systems, though it does not explicitly contrast with siblings.

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. With multiple sibling analysis tools, the agent has no criteria to choose this over others for specific tasks.

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

Deploy Server

Other Tools