Skip to main content
Glama
Sign In
Universal Game Modder

Universal Game Modder

by doritoman90000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

analyze_save_format

Inspects SaveManager classes in a specified assembly to reveal a game's save format, aiding modders in locating and understanding save data structures.

Instructions

Analyze game save system by examining SaveManager classes.

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": {
      "assembly": "<assembly>"
    },
    "name": "analyze_save_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
assemblyYesAssembly key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It reveals only the mechanism (examining SaveManager classes); it does not state that the operation is read-only/non-destructive, what permissions or loaded state it requires (the required 'assembly' key implies prior loading), or what the analysis yields. 'Analyze' is left completely unqualified.

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?

A single front-loaded sentence with zero filler. It is appropriately sized, though the brevity overlaps with under-specification rather than pure economy.

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?

No output schema and no annotations exist, so the description must explain what the analysis returns (e.g., save structure, serialization details, detected SaveManager types), and it does not. For an analysis tool that gates other workflows, this leaves the agent guessing about the result shape.

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?

Only one parameter exists and schema description coverage is 100% ('assembly: Assembly key'), so the schema already documents it. The description adds nothing about the parameter, but per the high-coverage rule the schema doing the work makes a baseline 3 appropriate.

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?

Names a specific verb (Analyze) and resource (game save system), plus the mechanism (SaveManager classes), so an agent knows the target. However, it does nothing to distinguish itself from adjacent analysis siblings like analyze_file_format, analyze_dll_structure, or analyze_pe_full.

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?

There is no when-to-use, when-not-to-use, or alternative routing guidance. The relationship to load_assembly (which presumably supplies the assembly key) or to save-related siblings is left entirely implicit.

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