Skip to main content
Glama
Sign In
agent-bridge

agent-bridge

by avas-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app.restore

app_restore

Undo changes an app's tools made during a session by running their registered onRestore undos once, newest first, and return how many ran.

Instructions

Undo what the app's own tools changed: runs the undos they registered with onRestore, newest first, once. Returns how many ran.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "app_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNoThe tool's arguments, in order (each any JSON value). Leave out for none.
fullNoReturn a result over 32 KB whole instead of a summary of its size and shape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose meaningful behavior: undos run newest-first, each runs exactly once, and the return value is the count that ran. It does not cover failure behavior (what happens if a handler throws), what occurs when nothing is registered, or whether restoration is idempotent across repeated calls.

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?

Two short sentences with the mechanism front-loaded and the return value trailing, which is a sensible order. The 'onRestore / newest first / once' clause is dense and jargon-heavy but every element is load-bearing.

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

Completeness3/5

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

It covers the core mechanism and the return value for a tool with no output schema and no annotations, which is most of what an agent needs. Missing are edge-case behavior (no registered undos, partial failure) and any signal about how it relates to the other restore tools in the catalog.

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 both 'args' and 'full' are already documented and the baseline is 3. The description adds no meaning about either parameter, and notably never explains why a restore operation takes 'args' at all, leaving that mapping to the schema alone.

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 gives a specific verb (undo) and a precise scope (changes made by the app's own tools, via their onRestore handlers), which separates it from bridge_restore and scenario_restore without naming them. It stops short of explicitly contrasting with those siblings, so the differentiation is implied rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied: you call this after the app's tools have done work that registered undo handlers. There is no explicit statement of when to prefer this over bridge_restore or scenario_restore, and no exclusion or precondition (such as requiring handlers to have been registered in the current session).

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

Deploy Server

Other Tools