Skip to main content
Glama
Sign In
agent-bridge

agent-bridge

by avas-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bridge.pending

bridge_pending

Shows what bridge.restore would undo right now by area, including pending store or app changes, without modifying anything. Use it to preview reversible agent changes before restoring.

Instructions

What bridge.restore would undo right now, per area (store, query, net, app, ...): the value is true, or detail such as a store's snapshot against its current value. Empty when nothing is pending. Changes nothing.

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_pending"
  }
}

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

A4.1/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 it does disclose the key trait: 'Changes nothing,' i.e. this is a non-mutating inspection. It also describes the return shape (true, or detail such as a snapshot vs. current value) and the empty case, though it says nothing about cost, permissions, or failure behavior.

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 short sentences, front-loaded with the core concept, and every clause contributes (scope, return shape, empty case, non-mutation). The parenthetical area list is slightly compressed but not wasteful.

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?

No output schema exists, so the description usefully explains what comes back and what emptiness means; combined with the non-mutation note, an agent can call this safely. Minor gaps remain around the positional args interpretation and any preconditions, which matter for a generic-args tool.

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 coverage is 100% with two generic parameters (positional args array and a size-override flag), so the schema already documents them. The description adds nothing about how the positional args map to areas or to bridge.restore, leaving the baseline of 3 appropriate.

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 precisely that this reports, per area (store, query, net, app), what bridge.restore would undo right now, and names the sibling bridge_restore as the reference point. An agent can distinguish this read-only probe from the restore action without opening either 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?

The framing 'what bridge.restore would undo right now' plus 'Empty when nothing is pending' gives a clear context for use — as a pre-restore check and to detect pending state. It stops short of an explicit when-to-use/when-not instruction or naming what to do if the result is non-empty.

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