Skip to main content
Glama
Sign In

SuprSend

by com.suprsend
OverviewDiscussionsAdmin

Roll back translations

translations_rollback
Destructive

Makes an archived translation version live again, as a new version: every file of the workspace becomes as it was in that version, so later changes go away from the live translations. The current live version cannot be the target. Find versions with translations_list_versions.

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": {
      "version": "<version>",
      "workspace": "<workspace>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "translations_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesAnalytics: why you call this tool, in 10-20 words. Say "a user", never names, emails, or IDs.
versionYesThe version number (translations_list_versions).
llm_modelYesAnalytics: your model ID, or "unknown".
workspaceYesThe slug of the workspace to act on. Call workspaces_list to find the valid values.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

NameRequiredDescriptionDefault
metaNo
resultsYes
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, but the description goes further by revealing the blast radius: 'every file of the workspace becomes as it was in that version, so later changes go away.' That whole-workspace overwrite is critical context the annotation alone does not convey, and 'as a new version' hints the rollback is itself recoverable. It omits auth/permission requirements, keeping it at 4.

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?

Three sentences, no padding: action first, then the destructive consequence, then the constraint and the companion tool. Every sentence earns its place and the most important information is front-loaded.

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 destructive mutation tool with an output schema and full annotations, this covers what happens to the data, where to find the target version, and what is disallowed. It leaves permission/auth expectations unstated, a minor but real gap.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are documented structurally, but the description adds genuine meaning for the `version` parameter: it must already be archived and cannot be the current live version, and valid values come from translations_list_versions. That constraint is not present in the schema.

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?

States a specific verb and resource ('makes an archived translation version live again, as a new version') and immediately scopes it to 'every file of the workspace.' An agent can distinguish this from translations_publish/save/get_version without opening any schema.

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

Usage Guidelines4/5

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

Names the discovery path ('Find versions with translations_list_versions') and gives an explicit exclusion ('The current live version cannot be the target'), which prevents a common failed call. It does not mention the alternative action (publishing a new translation) or any prerequisite ordering, so it stops short of the 5 bar.

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

All SuprSend 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