Skip to main content
Glama
Sign In
gametrans

gametrans

by Drhushi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

engine_option_set

Destructive

Sets private engine options such as external toolchain paths for a game localization project.

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_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo选项名（由引擎支持包约定）
valueNo选项值（路径等）
projectNo游戏项目根目录（默认当前目录）
workdirNo工作区目录，默认 <项目>/.gametrans

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare that this is a write operation with destructiveHint=true, so the agent knows it mutates state. The description adds scope ('引擎私有选项') and an example, but does not explain overwrite behavior, permissions, or other side effects of setting the option.

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 wasted words. It states the core action and gives a helpful parenthetical example.

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?

Purpose is clear and the schema fully documents the parameters, while annotations cover the mutation safety profile. However, the description omits usage guidelines and mutation side effects, leaving it at minimum viable completeness for a destructive setter with no output schema.

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 coverage is 100%, and all four parameters (key, value, project, workdir) are documented in the schema. The description mentions key/value implicitly via '选项' and gives an example, but adds no syntax or semantic detail beyond what the schema already provides.

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 gives a specific verb (设置) and resource (引擎私有选项), with an example clarifying the kind of option. It does not explicitly differentiate from siblings such as engine_option_clear or engine_options, but the set/clear/list distinction is strongly implied.

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 when-to-use, when-not-to-use, or alternative-tool guidance. The example hints at one use case, but prerequisites and selection relative to engine_option_clear, engine_options, or config_set are absent.

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