ksp-mods-mcp

Overview Schema Source Related Servers Discussions Admin

search_mods_tool

Find Kerbal Space Program mods by name, author, tags, or KSP version compatibility. Filter, sort, and page through results to locate the right mod.

Instructions

Search KSP mods by name, author, tags, and/or KSP version compatibility, paginated.

Args: name: Case-insensitive regex matched against mod identifier and display name. Examples: "engineer", "^MechJeb", "visual|scatter" author: Case-insensitive regex matched against mod author(s). A mod matches if any of its authors match. Examples: "sarbian", "squad|nertea" tags: List of tags to filter by. Examples: ["plugin"], ["parts", "resources"] tags_mode: How to combine multiple tags — "and" (mod must have all tags, default) or "or" (mod must have at least one tag). ksp_versions: KSP game versions to filter by. A mod matches if any of its released versions supports at least one of the given KSP versions. Uses prefix matching, so "1.12" matches "1.12.0", "1.12.5", etc. Examples: ["1.12"], ["1.11", "1.12"] sort_by: Sort order — "downloads" (default), "downloads asc", "name", "name desc", "download_size", "download_size asc", "install_size", "install_size asc", "updated", "updated asc". cached_only: If True, only return mods whose ZIP is present in the local CKAN download cache. Requires CKAN to have been used to download mods. limit: Number of results per page (default 20, max 100). offset: Pagination offset (default 0).

Returns JSON with keys: total, offset, limit, results. Each result has: identifier, name, abstract, tags, authors, max_ksp_version, latest_version, last_updated_at, download_count, download_size (bytes), install_size (bytes). Results include is_cached: true only for mods present in the CKAN download cache.

Input Schema

TableJSON Schema

Name	Required	Default
`name`	No
`tags`	No
`limit`	No
`author`	No
`offset`	No
`sort_by`	No	downloads
`tags_mode`	No	and
`cached_only`	No
`ksp_versions`	No

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

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: it discloses case-insensitive regex matching, match-any-author semantics, tags_mode combination rules, KSP version prefix matching, the cached_only requirement, and the conditional presence of is_cached in results. This goes well beyond a simple 'search' statement.

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 summary sentence is front-loaded, and the Args section is tightly structured with each parameter earning its place through concrete examples and operational details. No filler or redundant restatement of the schema exists.

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?

For a 9-parameter, 0-required search tool with no annotations, the description is complete: it defines all input behaviors, lists all sort options, clarifies the cache filter, and documents the response keys. An agent has enough context to select and invoke this tool correctly without further investigation.

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%, but the description supplies rich semantics for every parameter: regex examples for name and author, tag combination logic, ksp_versions prefix matching, sort_by enumerations, limit/offset defaults and bounds, and the cached_only behavior. This fully compensates for the schema's lack of descriptions.

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 opens with a specific verb and resource: 'Search KSP mods by name, author, tags, and/or KSP version compatibility, paginated.' This clearly distinguishes search_mods_tool from sibling tools like get_mod_tool (single mod lookup), list_tags_tool (tag enumeration), and index_status (index health).

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

Usage Guidelines3/5

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

Usage context is implied by the search-focused description and detailed parameter semantics, but it never explicitly says when to prefer this tool over get_mod_tool, list_tags_tool, or other siblings, nor does it mention any alternatives. The guidance is inferable rather than stated.

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

Deploy Server