Skip to main content
Glama
Sign In
agent-bridge

agent-bridge

by avas-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bridge.restore

bridge_restore

Undo all changes an agent made by running each *.restore tool in name order, with scenario.restore last, and return each result or error.

Instructions

Undo what the agent changed: runs every *.restore tool in name order, scenario.restore last, and returns each result or error.

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": "bridge_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.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a fair job: it discloses that execution is an aggregate fan-out over *.restore tools, that ordering is deterministic, and that per-tool results or errors are returned individually. It does not say whether execution halts on the first error, whether the operation is idempotent, or what partial rollback leaves behind.

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?

One sentence, front-loaded with the purpose, then the execution model, then the return behavior. No padding or redundancy.

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 zero-required-parameter orchestrator with no output schema and no annotations, the description covers purpose, ordering, and result reporting. The main residual gap is failure semantics — whether the chain aborts mid-way and what state that leaves — plus how `args` maps onto the invoked tools.

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 the schema already explains both `args` and `full`; the description adds nothing about either. Notably it does not explain how `args` (a generic positional array) is distributed across the many *.restore tools it invokes, which is the one thing the schema cannot convey.

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 uses a specific verb and object ('Undo what the agent changed') and explains the mechanism: it runs every *.restore tool in name order with scenario.restore last. That implicitly distinguishes it from the single-target siblings app_restore and scenario_restore as the aggregate rollback, though no sibling is named explicitly.

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 implied rather than stated: 'Undo what the agent changed' tells the agent the triggering situation, and the ordering note (scenario.restore last) is a useful execution hint. There is no explicit when-not guidance and no named alternative for restoring a single app or scenario.

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