Skip to main content
Glama
Sign In
agent-bridge

agent-bridge

by merlinh0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

discover_sessions

Find live and recently saved coding sessions an orchestrator can take over, including transcripts, titles, working directories, and last activity.

Instructions

Existing omp / Claude Code sessions the orchestrator can take over with adopt_session.

live: sessions running right now in a Tern pane (any window), with their transcript. saved: the most recent saved sessions on disk that are not running (include_saved, up to limit per engine), with their title, working directory and last activity. managed_as: the agent name when the session is already under the bridge's control.

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": "discover_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
include_savedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 burden and does disclose meaningful behavior: 'live' means running in a Tern pane in any window, 'saved' means on disk and not running, and results include transcript, title, working directory and last activity. It omits whether the call is strictly read-only in effect and any freshness or staleness notes for the on-disk listings.

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?

Front-loaded with the one-line purpose, then a compact labeled breakdown (live / saved / managed_as) that maps directly to what the agent needs. No filler sentences and no repetition of the schema.

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?

There is no output schema and no annotations, so the description must convey return shape, which it largely does by enumerating the fields per category (transcript, title, working directory, last activity, managed_as). Minor gaps remain around ordering, empty-result behavior, and combined limit semantics across live and saved.

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 0%, so the description must compensate. It does explain include_saved (include non-running saved sessions) and clarifies that limit applies per engine to saved sessions, which is real added meaning the schema lacks; however it never says whether limit also bounds live sessions or what the default behavior is when include_saved is omitted.

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?

The description identifies the exact resource (existing omp / Claude Code sessions) and its scope (those the orchestrator can take over), and explicitly names the sibling that performs the takeover, adopt_session. An agent can distinguish this discovery step from the follow-up 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 Guidelines3/5

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

Usage is only implied through the phrase 'can take over with adopt_session', which suggests calling this before adopting, but there is no explicit when-to-use statement, no precondition (e.g. must run before adopt_session), and no guidance on choosing include_saved true vs false for a given goal.

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