Skip to main content
Glama
Sign In

run.zero

by de.run-zero
OverviewDiscussionsAdmin

Restore release

runzero_restore_release
DestructiveIdempotent

Put an earlier published state back on the real site. Use the id from runzero_list_releases. This CHANGES what visitors see. It does not touch the code: anything changed since is still there and still waiting, so this undoes what is published, not the work. If the user wants an announcement removed rather than the whole site rolled back, edit the page instead — going back also removes every other change made since.

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": {
      "app": "<app>",
      "release": "<release>"
    },
    "name": "runzero_restore_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesName of the app
releaseYesRelease id from runzero_list_releases

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint/idempotentHint), it explains the actual blast radius: it changes what visitors see, does not alter code or pending work, and 'removes every other change made since.' That is exactly the kind of consequence detail annotations cannot convey.

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?

Front-loads the core action and the in-caps warning, then layers the nuance. Slight redundancy in 'still there and still waiting' and in restating the rollback-vs-edit point, but nothing is truly wasted for a destructive action.

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 two-parameter destructive mutation with no output schema, it covers consequence, scope, and the alternative action well. It omits failure modes and permission/auth requirements, which keeps it short of full completeness.

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 coverage is 100% and both parameters are already documented, so the schema carries the load. The description only reinforces where the release id comes from and says nothing about the 'app' parameter; 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 and resource: it puts an earlier published state back on the live site, and it points to runzero_list_releases as the source of the id. It also distinguishes itself from code-level operations ('does not touch the code'), though it never names the potentially overlapping sibling runzero_activate_version.

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

Usage Guidelines5/5

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

Gives a concrete prerequisite for the key parameter ('Use the id from runzero_list_releases') and an explicit alternative with its selecting condition: if the user only wants an announcement removed, edit the page instead of rolling the site back. That is a clear when-to-use / when-not-to-use split.

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

All run.zero toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources