BCD — Bridge Control Delegate

app_show_menu

Open the context menu (or pop-up menu) of an element of the latest app_snapshot, as a right-click does. Returns the app's new state with the next snapshotId, so no extra snapshot is needed. If the window changed, or a person used the keyboard or mouse in the app since the snapshot, nothing is done and the error comes with the current state to retry from. A sent action is not proof the task succeeded. Needs ui and process permission (operating apps can run programs).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "snapshotId": "<snapshotId>",
      "elementId": "<elementId>"
    },
    "name": "app_show_menu"
  }
}

Input Schema

Name	Required	Description
`deviceId`	No	Computer name or id from list_devices. Optional with one computer online or a default set.
`takeOver`	No	Only when the user says so: act even though another conversation is operating this screen, which then holds it no longer.
`elementId`	Yes
`snapshotId`	Yes
`workSessionId`	No	Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / takeOver

Added value: +{
+  "description": "Only when the user says so: act even though another conversation is operating this screen, which then holds it no longer.",
+  "type": "boolean"
+}

AddedOct 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the return contract (new state plus next snapshotId, no extra snapshot needed), the failure mode and how to recover from it, the caveat that a sent action is not proof of success, and the permission requirement (ui and process). No contradiction with readOnlyHint=false / destructiveHint=false, since this is a mutating interaction.

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 core action and analogy, then the return contract, then the failure path. Every sentence carries information, though the final sentence bundles two unrelated points (verification caveat and permissions) into one dense block.

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?

With no output schema, the description takes responsibility for describing the return value (new app state with next snapshotId), the error payload (current state for retry), and the permission prerequisite. That covers everything an agent needs before invoking a five-parameter UI-automation 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 60%; deviceId, takeOver, and workSessionId are documented in the schema. The description implies snapshotId means the latest snapshot and that a new snapshotId comes back, but elementId's meaning (an index into that snapshot) is only gestured at with 'of an element.' Marginal added value over the schema, so baseline 3.

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 ('Open the context menu') and resource ('an element of the latest app_snapshot'), and anchors it with a familiar analogy ('as a right-click does'). An agent can distinguish this from app_press, app_select, and app_increment without opening the 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?

Gives clear operating context: it works against the latest snapshot, and it explicitly describes the retry path when the window changed or a person interacted. It does not, however, name or exclude sibling tools (app_press, app_select) that act on elements, so the routing decision is implied rather than stated.

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

All BCD — Bridge Control Delegate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?