Skip to main content
Glama
Sign In
Galgame MCP

Galgame MCP

by YeXuanHs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

kirikiri_tjs2100_split

Extract TJS2100 sectors into a folder, generating a manifest.json and numbered .bin files.

Instructions

Dump TJS2100 sectors to a folder (manifest.json + NNNN_TAG.bin).

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": {
      "path": "<path>",
      "output_dir": "<output_dir>"
    },
    "name": "kirikiri_tjs2100_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
output_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description must disclose side effects and safety. It mentions dumping files but does not state whether it overwrites existing files, creates directories, or has any destructive potential.

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?

The description is a single front-loaded sentence with no filler. Every word contributes meaningful information about the tool's operation and output.

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 it is a write tool with no annotations or output schema, the description is too sparse. It omits critical details like whether the output directory must pre-exist, how the manifest is structured, and what the input path refers to.

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 0% and the description does not explain the parameters. It only hints at 'path' and 'output_dir' through the verb phrase, without defining formats, constraints, or required behavior.

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?

The description uses a specific verb ('Dump'), names the exact resource ('TJS2100 sectors'), and specifies the output ('folder' with 'manifest.json + NNNN_TAG.bin'). This clearly distinguishes it from sibling tools like import/export/merge.

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 on when to use this tool instead of alternatives such as export, import, or merge. The description lacks any contextual hints for tool selection.

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