Skip to main content
Glama
Sign In
gametrans

gametrans

by Drhushi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

config_path

Destructive

Reports the file path of each of the four configuration layers, helping AI agents locate config files for game localization projects.

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": "config_path"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.8/5.0
Behavior1/5

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

The description describes a purely informational lookup ("report where the files are"), while the annotations declare readOnlyHint=false and destructiveHint=true. These directly conflict: either the tool mutates state (and the description omits that entirely) or the annotations are wrong, and the description gives the agent no way to resolve which.

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?

It is a single short sentence with no filler and the purpose is front-loaded. It is arguably too terse rather than padded, and "四层" is left unexplained, which keeps it just short of full marks.

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?

The tool takes no required parameters and its schema is fully documented, so little is needed. But with no output schema, the description could reasonably say what the report contains (four layer names and their resolved paths) and how the layers are ordered; that is missing, and the conflict with the annotations is left unaddressed.

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%: both `project` and `workdir` carry their own descriptions in the schema, including the default resolution for workdir. The description adds no additional meaning about these parameters, so the baseline 3 is appropriate.

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 names a concrete verb (report/announce) and resource (the file locations of the four config layers), so an agent can tell this is a path-lookup tool rather than a value-manipulation tool like config_show or config_set. It does not, however, name or exclude any sibling explicitly, and the phrase "四层配置" is never defined.

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 statement of when to use this tool versus config_show, config_set, config_unset, or config_providers, all of which live in the same config family. The agent must infer the distinction purely from the name and one-line description.

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