Skip to main content
Glama
Sign In
gametrans

gametrans

by Drhushi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

engine_option_clear

Destructive

Deletes a specified engine-private option to adjust game localization settings, enabling precise control over patch generation.

Instructions

删掉一条引擎私有选项

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "engine_option_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo选项名
projectNo游戏项目根目录（默认当前目录）
workdirNo工作区目录，默认 <项目>/.gametrans

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: no indication of reversibility, whether the option is removed permanently, or what error occurs for an unknown key. Little value beyond the annotations.

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?

A single short clause with no waste, but it is under-specified rather than elegantly concise. It is front-loaded, which is a positive, but there is nothing else to front-load.

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 destructive mutation with no output schema and no guidance beyond annotations, the description is too thin. It never says that the option is removed from the engine config, whether a confirmation or permission is required, or how it relates to engine_option_set.

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?

All three parameters are documented in the schema at 100% coverage, so the baseline is 3. The description adds no meaning about which key identifies the option, which option namespace it targets, or how project/workdir interact.

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+resource (delete an engine private option), which is more than a tautology, but it is minimally specified and does not differentiate itself from the sibling engine_option_set beyond the opposite direction. An agent can guess its purpose but gets no scope details.

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 on when to use this versus engine_options/engine_option_set, no prerequisites, no note about whether the key must exist or what happens if it does not. Usage is only implied by the name and the word '删掉'.

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