Skip to main content
Glama
Sign In
Universal Game Modder

Universal Game Modder

by doritoman90000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

diff_assemblies

Compare two assembly versions to show method-level changes and type differences, helping identify what shifted between game DLLs.

Instructions

Compare two assembly versions to show changes.

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": {
      "old_assembly_path": "<old_assembly_path>",
      "new_assembly_path": "<new_assembly_path>"
    },
    "name": "diff_assemblies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 200)
show_methodsNoShow method-level changes (default: true)
new_assembly_pathYesPath to new version DLL
old_assembly_pathYesPath to old version DLL

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 and falls short: it does not state that the operation is read-only, whether it is expensive on large assemblies, or how results are truncated (the limit param defaults to 200). 'Show changes' is the only behavioral hint.

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 no filler or repetition. It is efficient, though arguably too terse to be maximally useful.

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?

For a comparison tool with no output schema, the description should indicate the shape of the result (e.g. added/removed/changed types and methods) and note the limit behavior. Neither is present, leaving the caller unsure what they will receive.

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 100%, so all four parameters (paths, limit, show_methods) are already documented in the schema. The description adds no extra meaning such as path format expectations or what show_methods=false suppresses, so the baseline 3 applies.

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?

The description gives a clear verb+resource (compare two assembly versions) and states the outcome (show changes), so an agent knows what it does. However, it does not distinguish itself from nearby siblings such as compare_binaries_detailed, compare_signatures, or jar_diff, which a caller must disambiguate.

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 guidance on when to prefer this over the other diff/compare tools in the sibling list. No prerequisites (e.g. assemblies must be loaded or on disk) or exclusions are stated.

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