Skip to main content
Glama
Sign In
spt-forge-mcp

spt-forge-mcp

by cebarks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Mod Versions

get_mod_versions

Get full mod version history with SPT constraints, download stats, Fika compatibility, and dependency details by mod ID.

Instructions

Get the full version history for a mod. Includes SPT version constraints, download counts, Fika compatibility status, and dependency info.

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": {
      "mod_id": "<mod_id>"
    },
    "name": "get_mod_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNoSort field, e.g. '-published_at' for newest first
mod_idYesThe mod's numeric ID
includeNoComma-separated relationships to include: dependencies, virus_total_links
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so description must carry burden. It states it retrieves version history (read-only) and lists included info, but omits pagination behavior, rate limits, or auth requirements.

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?

Single sentence with clear verb and resource. No fluff; front-loaded with purpose.

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

Completeness3/5

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

No output schema and 5 parameters with 60% coverage. Description covers what data is returned but not pagination, sorting, or include options, leaving gaps for effective use.

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

Parameters2/5

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

Schema coverage is 60% but description adds no parameter-specific meaning. It does not explain page, sort, include, or per_page beyond schema descriptions, missing an opportunity to clarify usage.

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?

Description clearly states the tool gets the full version history for a mod and specifies included data (SPT constraints, downloads, Fika status, dependencies). Distinct from sibling tools like get_mod which likely returns mod details.

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?

No explicit when-to-use or when-not-to-use guidance. Implied use is for version history, but no comparison with siblings like check_mod_updates or resolve_mod_dependencies.

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