keyshade-mcp

Official

by keyshade-xyz

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

rollback_variable

Restore a variable to a specified previous version within a given environment.

Instructions

Rolls back a variable to a previous version

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": {
      "variableSlug": "<variableSlug>",
      "environmentSlug": "<environmentSlug>",
      "version": "<version>"
    },
    "name": "rollback_variable"
  }
}

Input Schema

Name	Required	Description
`version`	Yes	Version number to rollback to
`variableSlug`	Yes	Variable slug to rollback
`environmentSlug`	Yes	Environment to rollback in

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'rolls back' but does not disclose whether it destroys current state, creates a new version, requires permissions, or is idempotent. The behavior of rolling back (e.g., reverting to a previous version's value) is implied but not explicitly stated.

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?

Single sentence with no wasted words. It is concise, but the purpose could be clarified with a bit more structure (e.g., indicating what 'rolls back' means).

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?

Given three required parameters and no output schema, the description is too minimal. It does not explain what rolling back entails (e.g., reverting to a previous version, creating a new version), nor does it mention return values or prerequisites. The absence of annotations increases the need for more context, which is missing.

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?

The input schema already provides descriptions for all three parameters (100% coverage), so the description adds no additional semantics beyond the schema. Baseline 3 is appropriate.

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 description clearly states the action 'rolls back a variable to a previous version' – a specific verb and resource. It distinguishes from siblings like rollback_secret (different resource) and update_variable (different action), but does not explicitly differentiate.

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?

No guidance on when to use this tool vs alternatives such as update_variable or rollback_secret. The agent is left to infer from the name and sibling list.

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