Skip to main content
Glama
Sign In

Resistance Tools

by io.github.TONresistor
OverviewDiscussionsAdmin

Rollback site

sites.rollback
Destructive

Rollback an owned TON Site to a retained release.

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": {
      "site": "<site>",
      "releaseId": "<releaseId>",
      "confirmSite": "<confirmSite>"
    },
    "name": "sites.rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
releaseIdYes
confirmSiteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not required to restate these. It adds context by specifying 'owned' and 'retained release', but does not disclose the confirmation mechanism or what happens to the site during rollback.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It focuses on the core purpose without unnecessary elaboration.

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

Completeness2/5

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

This is a destructive operation with 3 required parameters and no output schema. The description omits prerequisites, the role of confirmSite, and what the expected outcome or return value is. Annotations provide some context but do not fill all gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 0%, the description must compensate. It only vaguely alludes to 'releaseId' via 'retained release' and 'site' implicitly, but does not explain the critical 'confirmSite' parameter or its purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Rollback'), the resource ('an owned TON Site'), and the target ('to a retained release'). It distinguishes this tool from siblings like sites.delete and sites.publish_files by specifying the rollback to a previous release.

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 implies the tool is used when you want to revert a site to a previously retained release, but it does not explicitly state when to use it versus alternatives, nor does it mention any prerequisites or exclusions.

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

All Resistance Tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources