Skip to main content
Glama
Sign In
gametrans

gametrans

by Drhushi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

resource_term_import

Destructive

Import term data from a JSONL file to replace a game's termbook exactly, handling line splits, merges, and batch renames while logging each change; dry-run previews changes.

Instructions

整份换上：让术语书最终恰好是这份 JSONL 里的几行 —— 拆行 / 合行 / 批量改名一次做完，每一步都进变更日志

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": {
      "file": "<file>"
    },
    "name": "resource_term_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNo谁拍的板：human / user / agentagent
whyNo为什么这么改（记进变更日志）
fileYes那份 JSONL（形状同 termbook.jsonl：key / profile / constant / order / position）
dry_runNo只报「会改成什么」，一个字节都不写
projectNo游戏项目根目录（默认当前目录）
workdirNo工作区目录，默认 <项目>/.gametrans

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered structurally. The description adds real value by disclosing that '每一步都进变更日志' (every step is recorded in the change log), but it does not explain what happens to existing entries absent from the file or whether the change is reversible.

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 the bolded '整份换上' leading, so the core semantic is immediately visible. It is dense with em-dash clauses but no sentence is wasted; slightly crowded but effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive bulk-replace tool the description conveys the replacement semantics and change-log behavior, and the schema fully covers the parameters including dry_run. It still omits the disposition of removed/absent entries and any irreversibility warning, which matter for a destructiveHint=true operation.

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% and all six parameters are documented in the schema (by/why/file/dry_run/project/workdir), so the baseline is 3. The description adds no parameter-level detail beyond noting the JSONL shape, which is already in the file param description.

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 states a specific verb+resource: it makes the termbook end up exactly matching the given JSONL lines, explicitly covering splitting, merging, and batch renaming in one pass. This differentiates it from single-entry siblings like resource_term_add/resource_term_remove, though it never names a sibling outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: '整份换上' (whole replacement) and '一次做完' (all done in one shot) suggest this is the bulk alternative to doing splits/merges/renames individually. However, there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. resource_term_add), leaving routing to inference.

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