Skip to main content
Glama
Sign In
sandboxed-browser-mcp

sandboxed-browser-mcp

by smkamranqadri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Key

browser_key

Sends a single key or key combination to the focused browser element and reports the resulting screen changes.

Instructions

Sends one key or a combination to the element that has the focus: Enter, Escape, Tab, ArrowDown, PageDown, ctrl+a, cmd+shift+t. Reports the changes on screen.

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": {
      "key": "<key>"
    },
    "name": "browser_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesOne key or a +-joined combination, e.g. Enter, Escape, PageDown, ctrl+a, cmd+shift+t.
profileNoWhich browser profile (a separate signed-in session) to use. Leave it out for the default one; name another only when the user's task names it. Profiles: default.default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • addedInput schema / properties / profile
      Added value: +{
+  "default": "default",
+  "description": "Which browser profile (a separate signed-in session) to use. Leave it out for the default one; name another only when the user's task names it. Profiles: default.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv1.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / key / description
      Previous value: -"Key or keys joined with +, e.g. Enter, Escape, shift+Tab, ctrl+a"New value: +"One key or a +-joined combination, e.g. Enter, Escape, PageDown, ctrl+a, cmd+shift+t."
  3. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds real context by disclosing the focus dependency and that it 'reports the changes on screen' rather than returning a value. It stops short of stating failure behavior or whether the key persists across navigations.

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?

Two short sentences with zero filler: the action and its target come first, followed by the output note. Every clause earns its place and nothing is repeated from the schema beyond what is needed to illustrate key format.

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 two-parameter tool with full schema coverage and no output schema, the description covers the action, the targeting model, and the feedback shape. Only the profile parameter and the not-focusable failure case are left entirely to the schema.

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%, so both parameters are already documented in structured fields, including the examples for 'key' and the profile guidance. The description's examples restate the schema rather than adding syntax rules or edge cases, so the baseline of 3 applies.

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?

States a specific verb and target: 'Sends one key or a combination to the element that has the focus,' then enumerates concrete key values. The focus-targeting framing implicitly separates it from browser_type (text entry), though it never names a sibling to sharpen that boundary.

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?

The phrase 'to the element that has the focus' implies a prerequisite (something must be focused first, e.g. via click or find), but the agent must infer that. There is no explicit when-to-use versus when-not, and no mention of what to do if nothing is focusable.

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