Skip to main content
Glama
Sign In
Universal Game Modder

Universal Game Modder

by doritoman90000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

jar_edit_file

Modify a text file within a JAR archive using session ID, file path, and new content to patch game resources without full extraction.

Instructions

Edit a text file within the JAR.

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": {
      "session_id": "<session_id>",
      "file_path": "<file_path>",
      "new_content": "<new_content>"
    },
    "name": "jar_edit_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesFile path within JAR
session_idYesSession ID
new_contentYesNew file content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.6/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 but only implies mutation via 'Edit'. It does not say whether new_content overwrites the whole file, whether changes are in-memory until jar_repack, whether the target file must already exist, or what happens to the session's state.

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 short sentence with no filler and the action front-loaded. It is efficient, though its brevity borders on under-specification rather than genuine conciseness.

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 3-required-parameter mutation tool with no annotations and no output schema, the description is too thin. It omits the session-lifecycle context, persistence semantics, and the relationship to jar_repack/jar_close that an agent needs before invoking it.

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 both the parameter set and their meanings (file_path, session_id, new_content) are documented in the schema. The description adds no extra semantics such as content encoding or path-relative rules, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb (Edit) and a resource (a text file within the JAR), which is enough to understand the basic action. However, it does not distinguish itself from close siblings like jar_add_file_content, jar_hex_edit, or jar_restore_file, and 'edit' is left ambiguous (full replacement vs. patching) despite a new_content parameter.

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 use this tool versus jar_add_file_content, jar_hex_edit, or jar_restore_file, nor any stated prerequisites such as needing an open session. The agent must infer usage from the name alone.

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