Skip to main content
Glama
Sign In
gametrans

gametrans

by Drhushi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

agent_submit

Destructive

Submit an answer to a pending game localization order, returning it to the same validation chain to ensure consistent verification.

Instructions

交一份答案给挂单（只有 pending 的单能收；答案回到同一条校验链）

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

Input Schema

NameRequiredDescriptionDefault
answerNo答案正文（JSON：translations 数组，可选 terms）
projectNo游戏项目根目录（默认当前目录）
workdirNo工作区目录，默认 <项目>/.gametrans
request_idNo挂单 id（agent next 返回的那个）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a write operation (readOnlyHint=false) and destructive (destructiveHint=true). The description adds genuine context beyond them: only pending orders accept submissions, and the answer rejoins the same validation chain. It still does not disclose what 'destructive' means here (does resubmitting overwrite a prior answer?) — an important gap for a destructive tool.

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 the core action stated first and the constraints in a compact parenthetical. No wasted words, though very terse for a destructive write operation.

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?

There is no output schema, so the description should carry return/error behavior, and it does not say what happens on success or when no pending order is found. For a destructive write tool with zero required params it is minimally adequate but leaves the agent guessing about failure modes.

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 all four parameters (answer, project, workdir, request_id). The description adds nothing about parameter format or defaults, so baseline 3 applies.

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 (submit/交) and resource (an answer to a pending order), and the parenthetical clarifies the target is a pending 挂单. An agent can distinguish this from agent_next (which produces the order), though the sibling is not named directly in the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The constraint '只有 pending 的单能收' tells the agent when submission is valid (only for pending orders), which is meaningful guidance. However it does not name alternatives or state what to do if no pending order exists (e.g. call agent_next first). Usage is implied rather than explicit.

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