Skip to main content
Glama
Sign In
gametrans

gametrans

by Drhushi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

resource_style_add

Destructive

Add or overwrite a game localization style rule keyed by aspect and scope, so tone, dialogue, forbidden terms, and naming stay consistent across translated content.

Instructions

新增/覆盖一条风格要求（按 aspect + scope 定键）

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": {
      "aspect": "<aspect>",
      "value": "<value>"
    },
    "name": "resource_style_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo备注
scopeNo作用域：global / character:X / scene:X / unit:X / region:X
valueYes要求本身
aspectYes风格维度：tone / dialogue / forbidden / naming …
projectNo游戏项目根目录（默认当前目录）
workdirNo工作区目录，默认 <项目>/.gametrans
priorityNo优先级（越大越先注入）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true; the description adds the important detail that this is an upsert keyed by aspect + scope, so an agent knows an existing entry with the same key will be overwritten rather than duplicated. It does not discuss permissions, priority effects, or return behavior, keeping it short of a 5.

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 zero filler, and the overwrite key is stated immediately. It is arguably too terse for a 7-parameter mutation tool, which caps it below 5.

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 mutation tool with 7 parameters and no output schema, the description covers the core action and key semantics but omits how optional params like priority, project, and workdir interact and what happens to non-keyed fields on overwrite. Annotations carry the destructive profile, so the remaining gap is moderate.

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%, so all 7 parameters are documented in the schema itself; baseline is 3. The description adds only the key-composition fact (aspect + scope), which is a small increment over what the schema already conveys.

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?

States a specific verb pair (新增/覆盖 = add/overwrite) and resource (风格要求 / style requirement), plus the key composition (aspect + scope). It is clearly distinguishable from siblings like resource_style_list and resource_style_remove, though it does not name them explicitly.

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 vs resource_style_remove or resource_style_list, and no prerequisites stated. The upsert semantics are implied by 新增/覆盖 but the agent is left to infer the workflow.

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