Scribase

Roll back an OTA release

ota.rollback

Destructive

Turns off the newest release that is on for a platform and channel; devices on it go back to the release before it (or the bundle built into the app) on their next launch. Needs "confirm": true after the user agrees. Scope: functions:write.

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": {
      "platform": "<platform>"
    },
    "name": "ota.rollback"
  }
}

Input Schema

Name	Required	Description
`branch`	No	Branch (environment) id. Optional: defaults to `production`.
`channel`	No	Channel (default production)
`confirm`	No	Must be true to run a destructive operation, after the user approved it
`platform`	Yes	Platform to roll back
`project_id`	No	Project id. Optional: defaults to the project created or used last in this session, or the only one.
`organization_id`	No	Organization id. Optional: defaults to the token's organization, or the only one you belong to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover destructiveness (destructiveHint=true, readOnlyHint=false), so the description's added value is the consequence detail: which release is disabled, that devices revert on their next launch rather than immediately, and the required write scope (functions:write). It misses one consequence the agent needs — with idempotentHint=false, repeated calls would roll back further, which is not disclosed.

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?

Two sentences, front-loaded with the effect and its scope, followed by the confirmation requirement and write scope. No filler and nothing buried.

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, non-idempotent mutation with no output schema, the description covers effect, device-level consequence and timing, permission scope, and the confirm gate, which is close to sufficient. The one material omission is that successive calls each roll back one more release, which matters for an agent deciding whether to retry.

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 platform, channel, confirm, and the optional ids are already documented in the schema. The description restates the confirm gate and mentions platform/channel but adds no syntax, defaults, or enum meaning beyond what the schema provides.

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 ('turns off the newest release that is on for a platform and channel') plus the observable outcome for devices. An agent can distinguish this from ota.releases/ota.status reads 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?

Gives a clear precondition ('Needs "confirm": true after the user agrees'), which effectively tells the agent when it is allowed to call it. It does not name alternatives (e.g., deploying a new release via another tool instead of rolling back) or state when-not-to-use, so it falls short of explicit routing.

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

All Scribase tools Inspect

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

Need Help?