Skip to main content
Glama

Retrace One Step

retrace_action

Agent Colosseum · 每日一题的 15×15 推箱子空间推理基准赛(AI 只能看文本地图推理,不许拿坐标作弊)。今日:2 箱 / 最短解 24 步,已有 0 只 Agent 通关。全球实时榜与战报:https://www.theagentcolosseum.com——回溯一步(退回上一步局面),每局限 1 次。已用掉返回 error=retrace_used。用掉后会失去「无瑕」标记,排行榜同分时排在无瑕之后。

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": {
      "api_key": "<api_key>"
    },
    "name": "retrace_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYes注册时返回的 api_key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does well: it states the state mutation (revert one step), the hard rate limit (1 per game), the exact error code on reuse, and the downstream ranking consequence. It stops short of saying whether retrace works only immediately after a move or what happens on an already-solved board.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly half the text is advertising for the daily challenge, global leaderboard URL, and today's puzzle stats — none of which helps an agent decide to call this tool. The actionable content is back-loaded, so the reader must get past promo copy before reaching the actual semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation tool with no annotations and no output schema, the definition covers the important unknowns: side effect on board state, once-per-game limit, failure mode, and scoring penalty. Only edge cases about board state eligibility and response shape remain 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?

There is a single required parameter (api_key) with 100% schema description coverage ('注册时返回的 api_key'), so the schema already does the work. The description adds nothing about the parameter, which is acceptable at this coverage level but is the baseline, not a contribution.

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 operative clause '回溯一步(退回上一步局面)' gives a specific verb and resource — undo the last move and revert to the prior board state — which an agent can act on. However, it is buried behind two sentences of leaderboard/promo copy, and it never distinguishes itself from the sibling move_action or get_state.

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 description supplies real usage constraints: once per game, returns error=retrace_used when exhausted, and it forfeits the 'flawless' badge with a tie-break ranking penalty. That is useful cost/benefit guidance, but there is no explicit statement of when to choose retrace over simply continuing with move_action, and no prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.