Skip to main content
Glama
Sign In
gametrans

gametrans

by Drhushi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ui_policy_set

Destructive

Set visibility policies for game localization topics, marking them as user, agent, debug, or hidden to control what information is exposed during translation.

Instructions

设置某类信息对用户可见还是透明

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": {
      "topic": "<topic>",
      "visibility": "<visibility>"
    },
    "name": "ui_policy_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes主题（支持 前缀* 通配）
projectNo游戏项目根目录（默认当前目录）
workdirNo工作区目录，默认 <项目>/.gametrans
visibilityYes可见性

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 mark this as a write with destructiveHint=true, yet the description never warns that setting a policy can hide information from users, whether the change persists across sessions, or how it interacts with existing overrides. It also doesn't clarify that '透明' (transparent) means visible-to-agent-only versus user-visible, which is the core behavioral distinction.

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, front-loaded sentence with no filler, which is structurally fine, but its brevity borders on under-specification rather than genuine conciseness.

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, four-parameter mutation tool with no output schema, the description omits persistence semantics, precedence against ui_override/ui_hide, and the meaning of the visibility enum values. It is not complete enough for an agent to call it correctly in an ambiguous situation.

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 the schema already documents topic (with wildcard prefix support), project, workdir, and the visibility enum — baseline 3. The description adds no extra meaning about how prefix wildcards interact with existing policies or what the four visibility levels imply.

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?

The description gives a verb (设置) and a resource category (某类信息 / visibility policy), so the general intent is inferable, but it never states what a 'policy' is or how it differs from siblings like ui_hide, ui_override, or ui_clear that also manipulate visibility. An agent cannot confidently pick this tool over those from the text alone.

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 reference at all, despite six ui_* siblings that appear to overlap. Nothing tells the agent whether this is a persistent policy versus a one-off override or hide.

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