Skip to main content
Glama
Sign In
Galgame MCP

Galgame MCP

by YeXuanHs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

image_pack_xp3

Create XP3 archives from folders using the native XP3 writer, enabling asset packaging for visual novel localization and modding.

Instructions

Pack a folder into XP3 using the native XP3 writer.

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "image_pack_xp3"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes
versionNo
compress_indexNo
compress_contentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions 'using the native XP3 writer', which hints at the output format but does not disclose effects like overwriting, compression defaults, version handling, or required permissions. The schema properties (compress_index, compress_contents) imply compression behavior, but the description adds no context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence), which is efficient and front-loaded. However, it is under-specified even for a simple tool; it lacks any structural breakdown or additional context that would help the agent. It is not verbose, but the brevity borders on under-specification.

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?

Given the tool's moderate complexity (5 parameters, no output schema) and the existence of sibling tools with overlapping functionality, the description is incomplete. It does not cover return values, error conditions, or when to select this tool over alternatives. The rich sibling list emphasizes the need for more contextual detail.

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?

The schema description coverage is 0%, so the description must compensate. It does not explicitly explain any parameters. At best, 'Pack a folder into XP3' implies that 'input' is the folder and 'output' is the XP3 file, but the version, compress_index, and compress_contents parameters are entirely unaddressed. This is well below the baseline expected for a tool with 5 parameters.

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 clearly states the primary action ('Pack a folder into XP3') and the method ('using the native XP3 writer'), which is specific and understandable. However, it does not distinguish this tool from sibling tools like 'xp3_pack' or 'archive_pack', which likely have overlapping purposes.

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?

No guidance is provided regarding when to use this tool versus alternatives. There is no mention of prerequisites, typical scenarios, or exclusions. Given the availability of similar pack tools (e.g., xp3_pack, kirikiri_pack_patch), the lack of usage context is a significant gap.

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