Lists global timers defined in a save—including name, seconds, and countdown or stopwatch type—so you can inspect timer settings without modifying the scene.
List the global timers (全局计时器) defined in a save: name, seconds, countdown or stopwatch. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
| mapPath | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, and the trailing "Read-only" merely restates that. The genuinely additive part is the disclosure of the returned shape (name, seconds, countdown vs stopwatch), which matters because there is no output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One compact sentence with the resource and return fields front-loaded, plus a two-word safety note. No filler, though the parenthetical Chinese gloss consumes space without adding selection value for most agents.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Returning the field list is helpful given there is no output schema, but the definition leaves the one real unknown — how mapPath selects the save — unresolved. For a single-parameter tool that is the only gap an agent actually needs closed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for the single parameter mapPath, so the description must carry the burden and it does not. "Defined in a save" vaguely gestures at the target, but never says whether mapPath is a filesystem path, a map identifier, optional (required=0), or what happens when omitted.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clear verb+resource ("List the global timers defined in a save") with the returned fields enumerated (name, seconds, countdown or stopwatch). It doesn't explicitly contrast with the sibling scene_add_global_timer or the timer-display tools, but the read/list framing is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to call this versus scene_add_global_timer or scene_add_timer_display, and no stated prerequisites (e.g. must a map be open first?). The only contextual cue is the phrase "defined in a save," which implies scope but does not route an agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.