Skip to main content
Glama

Set a Hosted App's current version

set_app_current_version
DestructiveIdempotent

Make a stored app version current immediately (roll back); no rebuild is needed. Listed Roles now reach this version's recorded Requests; its calls_without_grant is never granted. Returns access_changes for Roles whose reach grew; each added_requests entry carries changes_data: true when the Request can change data.

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_id": "<version_id>"
    },
    "name": "set_app_current_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoApp slug; provide exactly one of slug or app_id
app_idNoApp UUID; provide exactly one of slug or app_id
version_idYesStored version UUID belonging to this app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare destructive=true and idempotent=true; the description goes further by disclosing the side effects (Roles now reach the version's recorded Requests, calls_without_grant is never granted) and the response contract (access_changes for Roles whose reach grew, changes_data flag). That is exactly the extra context annotations cannot carry.

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?

Three tight sentences, front-loaded with the action and its consequence, with no filler. The density of domain jargon (calls_without_grant, added_requests) makes it slightly harder to parse but nothing is redundant.

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?

There is no output schema, so the description's explanation of access_changes and changes_data is what makes the return value usable. Combined with full schema coverage, an agent has enough to call it correctly, though it could say more about whether the previous current version is preserved.

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%, so slug, app_id, and version_id are already documented including the mutually-exclusive slug/app_id rule. The description adds no additional parameter meaning, which is acceptable given the schema does the work.

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 ('Make a stored app version current immediately') plus the key qualifier '(roll back); no rebuild is needed', which implicitly separates it from publish_app_version. It never names a sibling outright, so differentiation relies on inference from 'no rebuild'.

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?

The rollback framing and 'no rebuild is needed' give a clear condition for choosing this tool over a publish flow. There are no explicit exclusions or named alternatives, but the usage context is unambiguous for the rollback case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources