ksp-mods-mcp

Overview Schema Source Related Servers Discussions Admin

list_parts_tool

Inspect parts included in a cached KSP mod ZIP. Returns total count, category breakdown, and per-part details like title, cost, and modules.

Instructions

List the KSP parts included in a mod's cached download ZIP.

Only works for mods whose ZIP is present in the local CKAN download cache (i.e., mods you have downloaded via CKAN). Use index_status to check whether ckan_cache_available is true, and search_mods with cached_only=true to find mods that are cached.

Parts are scanned from GameData/{identifier}/Parts/**/*.cfg inside the ZIP. Bundled dependencies under other GameData/ subdirectories are ignored. Titles are resolved from the mod's English localization file where available.

Args: identifier: Exact CKAN mod identifier (e.g. "HeatControl", "NearFuturePropulsion"). detail: Level of detail to return: - "summary": total part count and breakdown by category (cheapest) - "basic": per-part name, resolved title, and category (default) - "long": basic + cost, mass, tech_required, bulkhead_profiles, modules (list of supported module type names), unsupported_modules (list of unsupported module type names), resources (list of resource names). Use get_part_tool for full module and resource detail.

Returns JSON. On success: summary: {total_parts, categories: {CategoryName: count}} basic/long: {total_parts, categories, parts: [...]} Returns an error object if the mod is not cached or the ZIP cannot be read.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`detail`	No		basic
`identifier`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A5/5.0

Behavior5/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 of behavioral disclosure. It clearly states the ZIP-scanned scope, the GameData/{identifier}/Parts/**/*.cfg path, that bundled dependencies are ignored, that localization is used for titles, and that an error object is returned on failure. This is thorough and adds significant behavioral context.

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 detailed but every sentence adds necessary information. It is well-structured with a clear first-sentence summary, usage constraints, scanning behavior, parameter documentation, and return format. Nothing is fluff or repeated from the schema.

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

Completeness5/5

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

The description is complete for the tool's complexity. It covers prerequisites, parameter semantics, return structure for all detail modes, and error behavior. The presence of an output schema plus this rich description leaves no meaningful gap for an agent selecting or invoking the tool.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description fully compensates. It explains identifier with exact format and examples, and detail with all three allowed values, their meanings, the default, and a cost note. This is exactly the level of guidance an agent needs.

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 states a specific verb ('List') and a specific resource ('KSP parts included in a mod's cached download ZIP'). It clearly defines scope and differentiates itself from sibling tools like get_part_tool by focusing on enumeration rather than single-part detail.

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

Usage Guidelines5/5

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

The description explicitly states when the tool works (only for mods with ZIPs in the CKAN cache), provides concrete prerequisite checks via index_status and search_mods with cached_only=true, and directs users to get_part_tool for full module/resource detail. This is exceptionally clear usage guidance.

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

Deploy Server