Skip to main content
Glama

rollback_version

Destructive

Restores an agent, schema, trigger, or MCP server to a recorded version by replacing its current configuration with the selected version.

Instructions

Restore a resource from a recorded version, replacing its current configuration.

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": {
      "resource_type": "<resource_type>",
      "resource_id": "<resource_id>",
      "target_version": "<target_version>"
    },
    "name": "rollback_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
resource_idYesResource UUID
resource_typeYesResource type
target_versionYesVersion number to restore

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.4
    • changedInput schema / properties / resource_id / description
      Previous value: -"UUID do recurso"New value: +"Resource UUID"
    • changedInput schema / properties / resource_type / description
      Previous value: -"Tipo do recurso"New value: +"Resource type"
    • changedInput schema / properties / target_version / description
      Previous value: -"Número da versão para restaurar"New value: +"Version number to restore"
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description corroborates by naming what is overwritten ('replacing its current configuration'), which is useful context. It does not say whether the rollback itself is recorded as a version, whether it can be undone, or what permissions are required.

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?

A single tight sentence with the destructive effect front-loaded in a participial clause; every word earns its place and nothing is buried.

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?

For a three-parameter destructive mutation with no output schema, the description plus annotations cover the basic risk profile adequately. It omits what a 'recorded version' is, whether the current configuration is recoverable after rollback, and how it relates to the snapshot variant — gaps that matter for an irreversible write.

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%, with resource_id, resource_type (4-value enum), and target_version all documented inline, so the schema carries the parameter burden. The description adds no information about valid version ranges, cross-type behavior, or what happens on a stale target_version, 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 and resource ('Restore a resource from a recorded version') and adds the key consequence ('replacing its current configuration'). It does not distinguish itself from the sibling rollback_snapshot, so an agent cannot tell which rollback to pick from this text alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternative (rollback_snapshot) or how it differs. The agent must infer the trigger condition entirely.

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