Skip to main content
Glama
Erikdai

bridge-agent

by Erikdai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

launch

Open Windows apps, files, folders, or URIs and bring their window to the front; refocus if already open. Restricted to permitted items.

Instructions

Start a Windows app, open a file or folder with its default app, or open a URI, and bring that window to the front.

This is how a task leaves the browser: after launch, observe shows the native window with d refs. Launching
something that is already open only re-focuses its window. Apps, folders and files outside the user's permission
manifest are refused. Returns a RESULT line and a fresh observation of the new window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesWhat to open: a program name ('calc', 'notepad', 'excel'), a file or folder path ('C:\Users\me\Downloads\report.csv'), or a URI ('ms-settings:about'). Program names are resolved like the Windows Run box.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided the description carries the full burden and does so well: it discloses the refocus-instead-of-relaunch behavior for already-open targets, the permission-manifest refusal boundary, and the return shape (a RESULT line plus a fresh observation of the new window). These are exactly the behavioral facts an agent needs before invoking.

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?

Front-loaded with the three openable target types, then the browser-exit context and behavioral caveats. Most sentences earn their place, though 'This is how a task leaves the browser' is slightly narrative and could be tightened.

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?

Despite an output schema existing, the description still usefully sketches the return (RESULT line plus fresh observation), and it covers the permission boundary and refocus semantics for a one-parameter tool. Nothing needed to call it 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% and the single 'command' parameter is already well documented (program name, path, or URI, resolved like the Windows Run box). The description restates the same three input categories without adding syntax, quoting, or escaping details beyond the schema, so the baseline of 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 (start/open) and enumerates the exact resource types handled: Windows apps, files, folders, and URIs, plus the side effect of foregrounding the window. It is clearly distinguishable from siblings like navigate (browser-level) and observe (used afterward to see the result).

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?

Gives clear context for when this is the right call ('This is how a task leaves the browser') and routes the agent to observe for the follow-up step. It does not, however, contrast launch against navigate or focus_browser, which are the nearest alternatives for opening things, so the routing is helpful but not exhaustive.

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