Beat Saber Modding Tools MCP

Overview Schema Source Related Servers Discussions Admin

compare_versions

Read-only

Compares a manifest SemVer version against an assembly version using BSMT rules, treating 1.2.3 and 1.2.3.0 as equal and ignoring prerelease labels.

Instructions

Compare a manifest SemVer version with an assembly version using BSMT rules (1.2.3 == 1.2.3.0, prerelease labels ignored).

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": {
      "manifest_version": "<manifest_version>",
      "assembly_version": "<assembly_version>"
    },
    "name": "compare_versions"
  }
}

Input Schema

Name	Required	Description	Default
`assembly_version`	Yes
`manifest_version`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that by disclosing the normalization rules (1.2.3 equals 1.2.3.0, prerelease labels ignored), which materially changes how results should be interpreted. It does not say what happens with unparsable versions, but the output schema carries the result shape.

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?

One front-loaded sentence with no filler; the rule that determines the comparison outcome is stated immediately after the purpose.

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

Completeness4/5

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

For a simple two-parameter read-only tool with an output schema and annotations, the description covers purpose and the normalization rules that govern results. Only error/edge-case behavior and output interpretation details are absent, which are largely covered elsewhere.

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 description coverage is 0%, so the description must compensate; it does so partially by indicating that manifest_version is SemVer and assembly_version follows the four-part assembly format, plus illustrating the equivalence rule. It does not state argument order significance or accepted edge-case input formats, so compensation is incomplete.

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 (compare) applied to two named resources (manifest SemVer version and assembly version), which is clearly distinct from validation or read siblings such as validate_manifest, read_manifest, or get_assembly_info.

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 is only implied by the word 'compare' and the BSMT rule context; there is no explicit statement of when to call this rather than validate_manifest or set_version, and no prerequisites or exclusions are given.

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