Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

Reset a branch

branches.reset
Destructive

Throw away a branch's changes and take its parent's current data, in place: the URL and keys stay. Destructive: needs confirm: true and the destructive scope. Refused on production. Scope: branches: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": {
      "branch": "<branch>"
    },
    "name": "branches.reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchYesThe branch to reset
confirmNoMust be true to run a destructive operation, after the user approved it
project_idNoProject id. Optional: defaults to the project created or used last in this session, or the only one.
wait_secondsNoSeconds to wait until it is live (default 60, 0 returns immediately)
organization_idNoOrganization id. Optional: defaults to the token's organization, or the only one you belong to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds substantive context beyond them: the operation is in-place (URL and keys preserved), requires confirm: true plus the destructive scope, is refused on production, and needs branches:write. These are exactly the preconditions and side effects an agent must know before invoking a destructive call.

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 short sentences, each earning its place: the effect and in-place guarantee come first, then the destructive gate, then the production exclusion and scope. No filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive five-parameter tool with no output schema, the description covers effect, reversibility implications, required confirmation, environment restriction, and scope. Nothing an agent needs in order to decide and call correctly 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?

Schema description coverage is 100%, so branch, confirm, project_id, wait_seconds and organization_id are already documented. The description reinforces the confirm: true gate but adds no syntax, defaults, or meaning the schema does not already carry; baseline 3 applies.

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 (throw away changes) and resource (a branch), plus the crucial in-place detail: 'the URL and keys stay'. That distinguishes it cleanly from branches.restore (which would restore a prior state) and branches.delete, even without naming either sibling.

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?

Provides clear usage context — resets to the parent's current data, in place, and is refused on production, which is an explicit exclusion. It stops short of naming alternatives such as branches.restore or branches.delete, so the agent must infer that reset is not the tool for undoing or removing a branch.

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

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